Skip to content
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
Tuomas Kuosmanen edited this page Mar 26, 2018 · 4 revisions

Steve has worked with Openshift before or may still be working in that space.

He may not have a vast amount of mobile app development experience but wants a mobile perspective without having to become a fully fledged Mobile Application Developer.

He wants to understand how to add a mobile perspective to applications running inside Openshift.

UPS means "Unified Push Server" in this context.

Step Goals and Actions Feelings Notes
Starting point Needs to add Mobile perspective to OpenShift, wants to develop mobile applications Frustration: Having to learn everything about Mobile App development 1=:( 5=:)
Initial search Steve goes to google for "openshift mobile application" and finds AeroGear 3 SEO Notes
First visit and evaluation Steve visits the website and reads through the content 3 "Is this doing what I need?"
The key here is that Steve's problem is solved by AeroGear. Steve needs to see this very quickly. Should we have a problems AeroGear solves section? ,
add a mobile perspective to your existing application,
have an existing mobile app and want to secure it (auth),
have an existing mobile app and want offline capabilities (sync + auth),
have an existing mobile app and want to send it notifications (push),
do you have nothing but want a complete mobile solution (not sure if we want to take this on, we could)
Decision Steve decides AeroGear is up to the job, and wants to use it to send notifications to mobile devices from his OpenShift app. Steve needs to ensure that his App is in OpenShift and that its mobile enabled and then proceeds to follow the Push quick start guide. 4 Everything related to mobile apps, and their SDKs is new to Steve. "I like to learn from examples, a working example project is a good starting point". But there is quite a bit of initial installation of development tools.
Ensure App is in OpenShift Steve needs to ensure that his App is running in OpenShift. His App may already be in OpenShift, otherwise he will need to create a custom service/runtime which will represent his app. 4 An OpenShift cluster may exist or may need to be installed. Steve has experience in that, but there still needs to be links for OpenShift installation. The concept of 'making your App available in OpenShift' needs to be followed.
Provision UPS from Catalog Steve selects AeroGear Push from the OpenShift Service Catalog 5 "This is familiar stuff to me, though I need to figure out how to make my own app talk to the Push Server, but at least it's something I've done before in other projects."
Update code in my App to trigger notifications Steve will need to edit his code where he wants push notification to be triggered from and invoke the UPS Server API 2 A code update for Steve.
Bind my App to UPS Steve needs to make an association/binding between his App and the UPS Server, to allow his App to become the source of notifications which UPS will process. 2 This will be a deliberate user action which the Steve will invoke from the OpenShift UI. Behind the scenes the config needed by his App to talk with UPS will be injected into his App automatically.
Create a Mobile App Representation (MAR) Steve needs to represent the Mobile Client on the Server side (i.e. inside OpenShift). 2 "I will be using Android device for now at least".
Steve will, from the OpenShift Catalog, create an Android App, which provisions a Mobile App Representation inside his project in OpenShift. This MAR is a representation of the App on mobile devices.
Configure UPS Server to use FCM to send notifications Steve needs to configure the UPS Server to be able to make use of the Firebased Cloud Messaging which transports the notification to Android devices. 3 This will be done by editing the MAR and adding the google key to allow UPS Server communicate with FCM. Once this is complete, the server side is ready to send notifications.
Add Mobile UPS SDK to Mobile App Steve will need to add the UPS Mobile SDK to his Mobile App 2 "This is something I am not familiar with."
Question here is does Steve has a Mobile App to start out with; if not we need to link to a basic Build your first App for Android. Steve may need to follow that guide to get a basic App running. Then once a basic App is in place, the Mobile UPS SDK can be added.
Send a test notification to Mobile Device Steve wants to test if he has everything in place and setup correctly to allow for notifications to be sent to his Android Device. 4 Up to this Steve has been working inside of OpenShift and also on the client side mobile application. To test whether his Mobile Application can receive a notification from UPS, he is going to have to trigger a test notification. This will need to be done from the UPS Admin Application, which he hasn't had to deal with yet. Its a server side access to the UPS Server. There will be a link from his Android MAR, to the UPS Admin Application, so it can be launched from the MAR view inside OpenShift. Once launched, he will have to enter his OpenShift credentials to get access and then he will see the Android Variant which it a 1:1 mapping with his MAR in OpenShift. From there, there will be an option to send a test notification to his device.
End Result Steve has built his first mobile app that connects to his OpenShift backend and his backend app will trigger notifications to be sent to his mobile application, based on the business logic inside his backend app. 5

=

Clone this wiki locally