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
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
* 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.
On Tue, Mar 1, 2016 at 4:27 PM, Darren Coles <darrenc(a)wots.mobi> wrote:
> As I’ve seen your the one doing all the Safari Push notifications, I just
> wanted to ask if that’s in the latest release? 1.1.0 UPS
> I have everything setup, followed your blog to the letter and a few others.
> On the webpage via safari I get the popup for notifications and it
> registers it on the Aerogear UPS when I accept.
> In the UPS admin I can see the safari token.
> However when I send a message it always says successful, but nothing ever
> appears on the my system for notifications.
> I’m using the .P12 web.com.rhcloud.push-wots certificate with password,
> which is a web push certificate fro Apple.
> The backend shows successful even when I just send to the safari variant.
in the UPS, are you selecting the "production" option when uploading the
> (Will Safari work with normal IOS push certificate, trying that today as
> going around in circles at the moment.
> Can Aerogear actually handle Safari notifications and do you have a bit
> more of a HOWTO.
> The work on this platform is fantastic, and everything else works like a
> dream with all the mobile devices and chrome browsers.
> This is just the last thing that is driving me mad. And I can’t find any
> logs to tell me that anything is going wrong.
> If you could take a couple of minutes to point me in the right direction I
> would be so grateful.
I'm glad you like the platform. i haven't done any Safari work in probably
a year now, so things might have changed a little bit from when i wrote
that blog post, but if i get the chance, i'll try to go through it again.
> Thank you in advance, have a great day.
> Darren Coles
> mobile: 0420 908 356
> email: darrenc(a)wots.mobi
> web: http://www.wots.mobi
> The information in this e-mail is confidential and intended solely for
> the use of the individual to whom it was addressed. If you are not the
> intended recipient, please be advised that if you have received this e-mail
> in error then any use, dissemination, forwarding, printing or copying of
> this e-mail is strictly prohibited. If you have received this e-mail in
> error, please inform the sender by using the reply facility in your
> e-mail software and then delete from your system. Although Word On The
> Street, takes precautions to minimise the risk of transmitting computer
> viruses, it is your responsibility to carry out your own virus checks on
> this e-mail and any attachments. Please note that neither Word On The
> Street nor the sender accepts any responsibility for viruses. Internet
> communications are not secure and therefore Word On The Street. does not
> accept legal responsibility for the contents of this e-mail. Any views
> or opinions presented are solely those of the author and do not
> necessarily represent those Word On The Street.