To gather insights for DZone's Native Mobile App Development Research Guide, scheduled for release in February, 2016, we spoke to 18 executives who are developing mobile applications in their own company or helping clients do so.
Here's who we spoke to:
Dan Bricklin, CTO, Alpha Software| Adam Fingerman, Co-Founder and Chief Experience Officer, ArcTouch | Nishant Patel, CTO and Kurt Collins, Director of Technology Evangelism, Built.io | Tyson Whitten, API Management Product Marketing, CA Technologies | Rajiv Taori, VP Product Management Mobile Platforms Group, Citrix | Zach Slayton, VP Digital Technology Solutions, Collaborative Consulting | Brad Bush, COO, Dialexa | Craig Lurey, CTO and Co-Founder, Keeper Security | Jessica Rusin, Senior Director of Development, MobileDay | Steven Jovanelly, Senior Director, Innovation Lab, PGi | Brandon Satrom, GM Developer Platforms and Tools, Progress Software | Eddie de Guia, Co-Founder and Managing Director, PubNative | Hans Ashlock, Technical Marketing Manager, Qualisystems | Mark Kirstein, Senior Director of Enterprise Software, RhoMobile | Justin Bougher, Vice President of Product, SiteSpect | Carla Borsoi, Software Product Manager and Marketing Lead, 6SensorLabs | Lubos Parobek, VP of Products, Sauce Labs
We asked these executives, "What have I failed to ask that you think we need to consider with regards to native mobile app development?"
Here's what they said:
- Be friends with a good graphic designer (UX). There's a big variation in the skills of a developer and a designer. Team up with someone that can design your front-end so you can focus on the development of the application.
- Think about what we’re doing with the data. Do we need to collect all of the data we're collecting? What are we going to do with it? How do we keep it secure? In what form do we need to serve it back up?
- How do we balance the spectrum of options and get the experience to fit together. We need to ask customers “what do you want to see?” while also realizing, like Steve Jobs did, the customer may not know what is possible.
- Open source is what developers love. Github enables you to become familiar with the technologies, collaborate via websites, hackathons provide access to APIs.
- At the network level, how devices are interconnected and the underlying network infrastructure.
- Cross-platform development tool like Xamarin enables you to write once and use anywhere by compiling code. Everything depends on the business purpose of the app.
- I'm not very familiar with hybrid but I see the opportunity of providing a base-level of functionality. Over time that will evolve and we’ll have standards - especially on Android (Amazon and Samsung) which will enable us to put more focus on the business.
- The mobile developers of today are the IoT developers of tomorrow. End user experience, minimal bandwidth use, personalization are all critical. There will be more devices like Amazon Echo with Alexa. Anything with an API is a development platform.
- Tooling. Know what's available and what problem it solves. If you find something that works, stick with it. Don't chase shiny objects, they'll waste your time. Learn what's working for others' that may be able to help with your challenges.
- The future is a good question. More platforms are coming out and everything will be connected. Amazon Echo is very cool and has a native tool kit. Google will come out with a Google Now version to compete with it. Simple to do an integration with and have a voice command tool.
- Apps that are used globally need to consider network bandwidth. Apps that work well in South Korea don’t work so well in the U.S. - or other parts of the world.
Do you have any additional thoughts about the development of native mobile apps that we didn't address in the last 10 articles?