Mobility is now becoming the 1st screen instead of the 2nd screen and the backbone to a lot of enterprise applications. For a consumer-facing application, it has already become the mainstay.
Our mobility practices involve both building native codes and also using cross platform application tools like Ionic or Xamarin. Our portfolio of work primarily consists of enterprise mobile applications; but we have also developed considerable consumer-facing applications for a couple of startups in the aviation, laundry, taxi, and healthcare sectors.
We typically get involved at the wireframing stage but more often even at the ideation stage. Typically architecture comes under our scope of work, which is key to ensuring long-term satisfaction or in contrary dissatisfaction to an end user. This outcome is normally obscured and never becomes visible until the application reaches critical mass; but by then it becomes too difficult to change the architecture as the application would already be falling apart at the seams.
We do quite a bit of consultation service and market surveys to understand the end user profile, usage behavior, and infrastructure to understand what kind of UI and UX would be suitable, as on several occasions we bring the data to mobile to support offline processing to ensure service availability in low connectivity zones.
Typical workflow involves:
- Iterative development
- Release / handover