Soyez le premier à aimer ceci
The consumer is spoilt for choice. Most of the buzz is around apps that individuals consume. Why? Because apps are sexy, provide unique experiences. Consumer discover new things to do, or new ways of doing existing things. Many are now billion $ brands with global recognition. Take Facebook, which has seen meteoric growth since it embraced mobile.
But there is another market, which frequently gets overlooked. This market is:
- Not sexy
- Not looking for unique experiences
- Has its own unique set of challenges.
But this market has 1 unique characteristic: It has in-built buyers.
Who am I talking about? The employees!
The global workforce is 3 Billion. The white collar workers are tech savvy, well educated, already using consumer level apps on their own mobile devices.
How does this make them a captive audience? The magic word: Apps for the Enterprise.
Reality Check: Nearly 3/4th of the enterprises have built less than 5 apps, of which 40% is at 0-1 app only for their employees.
According to Gartner, by 2017, 25% of all enterprises will have app stores. Companies will invest in HTML5/Hybrid apps to fulfill demand from employees for apps.
Why should developers go for it? The market is growing. A Nasscom report says the Enterprise Mobility market is expected to be worth $140 Billion by 2020.
What about enterprises?
- People bring own devices, clamor for support from companies
- IT no longer controls budget, biz units are recognizing a need for such initiatives and building their own apps
- Biz units bypass corporate guidelines in order to access data faster & collaborate more effectively
Unfortunately businesses fail at building effective apps.Most apps are the result of squeezing a web app onto a mobile device.
Companies need to focus on 5% principle. A mobile app will have only 5% features of the web app, but features that drive the most value.
How to become Mobile First? Use Business Architecture approach
1. Identify your stakeholders
2. Map your current & potential modes of engagements with stakeholders
3. Evaluate the engagements vis-a-vis business strategy
4. Identify capabilities required to support these engagements
5. Cost/benefit analysis of building new engagements
Mobile Maturity Lifecycle:
- Opportunistic: No central mobile strategy, one off mobile projects
- Strategic: Strategy varies by business unit, development tools & resources in place, but not optimized for scale
- Mobile First: Central strategy tied to business metrics, IT governance balanced with business data needs, scalable development methodology
Key Challenges to Mobility: Supporting employee devices, managing security, configuring new & legacy systems, go native/hybrid, managing pvt app stores
BaaS - An alternative to mobile middleware. Complexity of building a backend can be time consuming & expensive.
By de-cluttering the backend of app development, developers can focus on the user experience and the app itself.