There’s one thing about custom mobile development that everyone wants to know: What will my mobile app cost?
- Establishing a product roadmap to create progressive value. Expect that you will incrementally implement product features over time, most likely starting with a “minimum viable product” (MVP) release (see also Does an MVP Release Make Sense for Your Mobile Initiative?).
- Establishing a product release plan with a cadence to support a “test and learn” approach. Your ideal release cadence will be dependent on many factors. A few principles are in play:
- You will make mistakes of all sorts. No one gets it 100% right the first time or can afford to rest on their laurels. Users will generally forgive mistakes that are quickly addressed in a new release.
- It’s much more effective to try a few new features that you can discretely evaluate than to roll out a ton of new features at once. This implies frequent, small releases.
- The device landscape will change rapidly. New operating systems versions, new devices, security issues, as well as other changes will require you to update your app in order to remain operationally viable. (Yes, you will be subject to less flux due to these factors in a private enterprise mobile app where you control devices and deployment.)
- The competitive and market landscape will change rapidly. Mobile is a key point of both competitive differentiation and innovation. Expect that both competitive pressures and technical innovations will require you to regularly re-prioritize your product roadmap and release plans.
- Identifying and empowering a product owner. This person must have the business and technical acumen—as well as the authority—to quickly make product decisions to direct the product development team’s work. Ideally, they have product P&L responsibility and report in to a product management organization or business unit, not IT.
- Product Owner / Product Manager with mobile product management skills (see also Magenic Technologies' Product Owner or Product Manager?)
- Mobile Architect with mobile application architecture and enterprise integration skills
- Mobile Developers with specific experience and expertise on your chosen development platform and technology stack, including the ability to integrate supporting systems
- Mobile User Experience Designers who understand mobile devices, mobile interaction design, your chosen platform’s design guidelines, and mobile design/prototyping tools
- Mobile QA Engineers who with deep understanding of mobile device functionality, context and interaction models, mobile test strategies and tools, and an ability to test data at the code level
“What we’re learning is that creating the world’s coolest mobile app isn’t going to do any good if your infrastructure can’t support real time interactions with your ERPs, and other business solutions and processes on the back end. Mobile applications are driving this digital transformation back into the enterprise. CIOs are saying, ‘We have to do this in order to be competitive, because more and more of our business is being transacted through our mobile applications.’”