ah, ok - too bad none of that was here on the list :)

On Thu, Feb 25, 2016 at 12:11 PM, Corinne Krych <corinnekrych@gmail.com> wrote:
@Matt I've submitted a proposal around Watch SDK as I've recently being reached by a student still interested by this 2015 subject.
So here is the abstract:

WatchKit SDK for AeroGear/FeedHenry

Summary of idea:

Bring the features of AeroGear/FeedHenry libs to the  Watch:

- push notification

- geofencing

- oauth2: send a tweet from your wrist…

Provide an extension to the existing AeroGear sdks to make them Apple Watch fit. Focus on high quality sdks also include work on how to unit test (mocking…) your app. 

Knowledge prerequisite: iOS8/9, Swift

Skill level: Medium

Associated project(s): AeroGear, FeedHenry, Keycloak



On 25 February 2016 at 12:04, Matthias Wessendorf <matzew@apache.org> wrote:
Any other thoughts/ideas for GSoC 2016 ? 

On Tue, Feb 23, 2016 at 12:40 PM, Matthias Wessendorf <matzew@apache.org> wrote:

for GSoC 2016 we have not discussed our participation on this subject. I'd like to get a new and modern version of AeroDoc in.

Here is some text that I came up with:

AeroDoc Demo case for Unified Push Server

Write a new versions of the different components for our successful AeroDoc example, which you can see here

Backend/Server microservice component
* remove picket link based auth with Keycloak for pure OAuth2 login
* convert the server to WildFly Swarm fat JARs, to run AeroDoc as a Microservice, in a scalable mode.
** Features like WildFly's Ribbon layer (from Netflix OSS) could be used
* Rewrite the UI, using Angular2 and make it look nicer :)
* Use latest of Hibernate's Geo library for Geolocation based push notifications
IMO it could be done as a complete rewrite.

iOS app update:
* port the application to Swift and use our Keycloak library for OAuth2

Android app update
* port app to latest Android APIs and use our Keycloak library for OAuth2

New Windows version of the App
* would be nice to have

New feature:
* Silent notifications:
Introduce the usage of silent notification (no alert) to ping the application. The app wakes up, and performs a HTTP background check against the backend, to check for new Leads (for the AeroDoc Sales guys). Based on the HTTP response of the call, done in the background, local notifications are issued and presented to the user. This includes fine grain update of badge icon on iOS, and similar techniques on Android.


I think the above would make a good exercise of a student, interested in mobile app development, that also deals with an interesting use-case (Geolocation, OAuth2 and Push), as well as backend interaction.

Any thoughts?


aerogear-dev mailing list

aerogear-dev mailing list

Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf