The Apsima UI SDK provides a variety of pre-built UI components including mobile profile, notification, and payment widgets to allow developers to more quickly develop polished apps utilizing Apsima’s rich features. For this we also provide our developers with a complete mobile reference app to leverage during development as a base to get them started. View our reference app screens in the sections below to orient yourself with some of the features the UI SDK provides.
It is also important to note that all views included in the UI SDK can be customized to match your branding. Here are a few examples of fully customized apps utilizing our UI SDK with unique layouts, color schemes, and menu options.
Developers can leverage Apsima’s fully customizable profile widgets to quickly add login, sign up, edit profile, etc. to his or her app.
Login: Once the user has created an account they can login using their credentials created during sign up.
Forgot Password: If the user has forgotten their password they can reset it and receive a temp password via email.
Account: By touching their profile photo the user can adjust their account profile including changing their photo.
Edit Profile: The user can change their name, username, and email address by selecting Edit Profile under their account view.
Developers can use our fully customizable mobile notification widgets to quickly create apps that receive, display, and delete notifications.
Notification Settings: From the settings view the user can navigate to configure notification specific settings including whether they want email payment receipts.
Badges: The app keeps track of all unread notifications across all user devices. Badges are visible from the main menu.
Notification Banner: User can see a notification banner with each notifcation received when inside the app.
Notification View: User can view all read and unread offers by navigating to the offers view from the main menu.
These flexible payment widgets provide all the UI to manage payment accounts, accept a signature, process credit cards, etc.
Payment Accounts: From the account view the user can add multiple credit cards to be used for future one-click payments.
Credit Cards: Each credit account can be entered and saved for future use. No account numbers are actually stored, as the system utilizes a 3-token system of security.
Payment History: Under the main menu the user can view a complete payment history of past purchases.