Users and devices
Identify customer or staff roles, supported iOS and Android devices and required accessibility or language needs.
Portfolio
Mobile application portfolio
Review selected mobile app projects for customer and operational use. Device requirements, network conditions and back-office connections are useful points to compare alongside the screens.
Selected mobile application work
Showing all 17 projects
-
Business Advisor
iOS & Android
-
Empire Sushi
iOS & Android
-
Southern Health
iOS & Android
-
GS Motoring
iOS & Android
-
Floor Depot
iOS & Android
-
Momento.la
iOS & Android
-
Islamic Financial Services Board
iOS & Android
-
SnapMonitor
iOS & Android
-
My Interface Hub
iOS & Android
-
RSVPEY
iOS & Android
-
E-Pay
iOS & Android
-
MyCar
iOS & Android
-
Yelo!
iOS & Android
-
eClub Store
iOS & Android
-
Bus Buddy
iOS & Android
-
Cam Up
iOS & Android
-
Warranty Success
iOS & Android
A selection of the mobile applications we have delivered. Ask us for a walkthrough of the closest comparable build in your sector.
21+
Years in Business
900+
Projects Delivered
26
Countries Served
100%
In-house Malaysian Team
Review the mobile journey in context
Discuss who uses the app, where they use it and which information comes from a backend system. A visual example is only one part of the scope.
Device functions
Review camera, location, notifications and file access. Agree what happens when permissions are denied or connectivity is lost.
Release and operation
Include testing, account responsibilities, app updates and backend support in the discussion. Confirm the deliverables for your own project.
Questions about our mobile app portfolio
What should we look at when comparing mobile app examples?
Look at the tasks users complete, how often they return and whether the app needs payments, offline use or device features. Those requirements are more useful for planning than the number of screens alone. Backend and administration work should be considered too.
Can UNO build an app for both our customers and staff?
Yes. Customer and staff functions can be scoped together, with separate access where needed. We assess whether one app or separate interfaces would be easier to use and maintain. UNO's mobile development uses Ionic, Angular and Capacitor for iOS and Android.
Do mobile app screenshots show how an app behaves offline?
No. Screenshots do not show what happens when a connection drops, an upload fails or a permission is denied. If those conditions matter to your users, include them in the brief and demonstration questions. Offline behaviour needs to be specified and tested as part of the workflow.
What should we prepare when discussing an app portfolio example?
Describe the user's task, the devices they use and how often they open the app. Identify any camera, location, notification or offline requirements. Explain which existing system holds the account and transaction data so the discussion covers the backend as well as the screens.