Overview | Backend | App Configuration | Android | iOS |
MBO Android App | OData Android App |
OData Android Content:
On-boarding is the process of registering a user and giving them appropriate access to data and applications. MBO based mobile apps built in SUP 2.x/SMP 2.3 must register with the server before establishing a connection. Similarly OData based mobiles apps built in SMP 3.0 must on-board with the server before accessing backend data. However, this registration process for MBO based apps is completely different from the on-boarding process for OData based apps. In consequence, developers who want to migrate android apps from MBO to OData are required to rewrite the login screen. In the following section, we will compare both registration processes to guide your through these changes.
MBO Based Mobile Apps
In order for MBO based mobile apps to register with the server during the initial application startup, developers must:
OData based mobile apps
On the other hand, OData based mobile apps built using SMP 3.0 can leverage the MAF Logon component to simplify the on-boarding process. The MAF Logon component provides with the user interface and the logic required to onboard users.
In order to use the MAF Logon component, developers must
You can find in this guide How To... Setup MAF resources in Android Studio details about how to:
Below you will find screenshots of the LoginActivity for the sample MBO based app and the OData based app.
Please note we have submitted this sample app for publishing and it will be available on a public Git repository soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
10 | |
10 | |
10 | |
8 | |
7 | |
7 | |
7 | |
7 | |
6 |