Jason, > On 07 Dec 2015, at 15:12, Jason H <jh...@gmx.com> wrote: > > I do mobile, so some of the limitations of Qt are starting to become > apparent. In particular: > > 1. Local/Push Notifications support. We need platform independent coverage. > Each platform provides the same basic approach to binding to push > notifications. > I have boilerplate code for iOS that I can supply. It may or may not be up > to Qt's standards. It's in Obj-C. What is required is an android version and > then the Qt abstraction layer. Complicating matters is Apple, Google, > VPlay, and Amazon all have their own their back ends, and the architecture > should work with them all. (But minimally Apple & Google) (It also seems that > google has libraries that work on Apple as well. )
I use Parse to handle Push notifications for me (www.parse.com <http://www.parse.com/>). Have you tried it? It saves you a lot of hassle. > > 2. Background processing support. I wish to provide functionality when the > app is not running. Specifically for me, this is for a background upload > feature, but I'm sure there a multitude of other uses. I understand that iOS > is different, but Qt I think could provide the abstraction so that apps can > use background processing in a platform-abstract way. Out of my scope but also interested. > > Also, I'd be interested in knowing if there are any resources that already > cover these as my own searches have not turned up much. > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > <http://lists.qt-project.org/mailman/listinfo/interest> Best, Nuno
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
