The mobile app
development zoo
A little story: project
Imagine ourclient has a plan for a new website. We are invited to listen to the ideas.
A little story: target audience
We talk about the different audiences that need to be targetted with the appropriate content.
A little story: solution
PHP .NET PHP & Cloud
After a few days we come back with a plan to build the website three times. Once for each target group using the most appropriate techology for that group.
A little story: burnout?
You’d have to conclude: ‘this consultant either has a burn out or he’s taken up drinking!’
A little story: conclusion
Today, in mobile development, we are choosing who to service by making technology choices. ‘We like all our customers but the ones with certain devices we like even better’. And if we want to like them all equally, the investment in native development is huge.
Why go native?
Main advantages
• Marketing / distribution
• Sky is the limit in terms of design/animation
• Speed
• Offline
• Hardware
Why go native?
Main disadvantages
• Device & OS fragmentation (expertise & cost)
• Maintenance
• Updates
• Approval process
• Split revenue
Are there alternatives?
For this presentation we have investigated 34 different solutions.
Need for objective criteria
• We have chosen criteria to compare and distinguish between these different alternatives and applied them to 34 mobile development solutions
10
Architecture of Input/output
Technology/programming language(s) used
Support for which mobile platforms
Type of service model (cloud/on premise)
Conclusion: no one size fits all
• Native apps
• Code generation
• Off the shelf connectors
• Hybrid apps
• Webapps
• Mobile sites
Contact us if you want to know the details
• Ines Vanlangendonck – [email protected]
– +32 498 611573
– @niske
• Pablo Cacciatore – [email protected]
– +32 472 580555