Mobile Manifesto for Hybrid Development
Best practices for hybrid development are still evolving. We’re seeing many projects (by others) taking longer than they should, because it’s just not clear how best to design and construct hybrid applications for large-scale, mission-critical projects. The details would probably take an entire series of blog posts to cover.
So, I thought it would be helpful to share some of our rules of thumb for streamlining hybrid development. Like all articles of faith, some of these maxims may be contradictory. Keep in mind, that every situation is different and you’ll almost always have to make judgement calls (hence, the contradictions).
Of course, feel free to contact us if you’d like to discuss your specific situation.
- Use open solutions and interoperable components – the market is moving too fast for closed solutions to keep up
- Use HTML5 UX where possible
- Use Native UX for complex controls
- Determine UX on a feature-by-feature basis
- Push as much functionality into the cloud as possible
- Use analytics as much as possible (Google Analytics, Tealeaf)
- Responsive design is your base, with channel-specific optimizations as necessary
I expect this list to evolve over time. Our apps were built using these principles. We’ve also built some reusable infrastructure that uses these principles in an application agnostic way to speed up projects.