There's more to mobile development than simply choosing between a native or hybrid design. But far too often, architects embarking upon a mobile development strategy fail to address the other pertinent issues that need to be resolved early on in the software development lifecycle.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
"The most common mistake architects are making is that they aren't thinking in a broad enough context. They are just thinking in terms of 'should I build a mobile application' or 'should I build a native app.' There are a lot more issues to think about," said Anne Thomas Manes (@atmanes), a VP and Distinguished Analyst at Gartner.
So what else should enterprise architects and application designers be thinking about when entering the mobile space? Here's a nonexhaustive list of questions development teams should be asking themselves to ensure they are on the right track when it comes to building for the mobile space:
- How do you want to deploy the app?
- Where do you want the application to run?
- Do you need to isolate the app from other processes?
- Do you need to isolate the data?
- Do you need to keep data on the device?
- Do you need to synchronize the device with the back end?
"There's all of these different dimensions that go into this architectural model, so you have to make sure you've come up with the right set of questions to help you determine what is the right architecture," Manes said.
Manes really is one of the most compelling and informative leaders working in the mobile space. Watch the full interview to garner more insights from Anne about mobile architecture, security, and effective mobile development strategies.