[aerogear-dev] iOS Roadmap (updated)

Kris Borchers kris at redhat.com
Tue May 21 08:47:13 EDT 2013


On May 21, 2013, at 7:44 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Tue, May 21, 2013 at 2:34 PM, Kris Borchers <kris at redhat.com> wrote:
> 
> On May 21, 2013, at 7:30 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
>> Thanks for reviewing.
>> 
>> For iOS, I can see that adding SQLite is not that hard - perhaps I'd prefer moving the "Offline" to 1.3.0.
>> NOTE: CoreData is still optional - can could be done, if really wanted in 1.3.0 or in 1.4.0, after the data-sync
> 
> I tend to think Data Sync should come before Offline.
> 
> Android and iOS do have already "offline" storage bits (SQLite in Android; PList in iOS).
> For iOS this really means adding an SQLite impl of the vanilla AGStore protocol.
>  
> Even though you can have offline apps without Data Sync, they aren't that useful, especially in an "enterprise" environment. Most of the time, I would think you are doing things offline that you want to sync when you come back online.
> 
> Using Reachability APIs, this can be already done today.
>  
> That is why JS will do Data Sync before Offline so that we don't have to circle back and make them work together but I guess it could go either way.
> 
> :-) yeah - I feel like adding the Reachability support later, to make sure - it perfectly works with our different stores (PList, SQLite, …)

I guess that all makes sense. Offline and Data Sync are probably much more complicated for JS so I think the order matters there but probably not for Android and iOS.
> 
> -Matthias
>  
> 
>> 
>> -Matthias
>> 
>> 
>> On Tue, May 21, 2013 at 2:20 PM, Kris Borchers <kris at redhat.com> wrote:
>> 
>> On May 21, 2013, at 4:28 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>> 
>>> Hello,
>>> 
>>> today, Corinne, Christos and I met, and we iterated over the iOS roadmap. This is now (or should) match the "timeframe" of what QMX has posted earlier.
>>> 
>>> Please take your time and review it!
>>> 
>>> Thanks!
>>> 
>>> 
>>> iOS ROADMAP
>>> 1.1.0 (mid June)
>>> 
>>> Library
>>> AEROGEAR-1090: Add HTTP digest authentication support on AeroGear iOS
>>> AEROGEAR-1093: Add HTTP basic authentication support on AeroGear iOS
>>> Unit Tests
>>> AEROGEAR-1185: iOS: Evaluate the OHHTTPStubs project
>>> Xcode:
>>> AEROGEAR-1063: Xcode template: include OTP option
>>> AEROGEAR-1229: Update aerogear-ios-xcode template to include Basic/Digest auth options
>>> supported by doc updates
>>> 
>>> 1.2.0 (Mid August)
>>> 
>>> Unified Push
>>> AEROGEAR-1036: Unified Push Client library for AeroGear's iOS clients
>>> Travis CI: build hooks
>>> Tests...
>>> Demo application (supported by "iOS Push Tutorial")
>>> 1.3.0 (Mid October)
>>> 
>>> Pipeline
>>> Multipart support (AEROGEAR-1141)
>>> DEMO/Docs Crypto work:
>>> Implementation and API usage for iOS crypto (AEROGEAR-1150)
>>> DEMO/Docs
>>> 1.4.0 (Mid January)
>>> 
>>> Data Sync:
>>> see AEROGEAR-830 and linked JIRAs
>>> Offline
>>> better CoreData integration: see AEROGEAR-812
>>> SQLite support
>>> Notifications: somewhat belongs to Data-Sync and Offline support??
>> 
>> So qmx made a good point here on the JS roadmap so I thought I would do the same. Data Sync and Offline in a single release seems like a lot of work. I moved Data Sync up to 1.3.0 on the JS roadmap to break up some of that work. Just a suggestion.
>>> supported by doc updates
>>> 
>>> 2.0.0
>>> 
>>> iSocial ??? :)
>>> abstract integration
>>> MQTT for notifications ?
>>> TBD
>>> 
>>> 
>>> 
>>> 
>>> Thoughts? If OK, I'll move forward, and add it to our HomePage...
>>> 
>>> -M
>>> 
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130521/9804a213/attachment-0001.html 


More information about the aerogear-dev mailing list