- Defining the mobile beast
- User expectations trump developer benefits
- Questions to ask before you start
- Four paths to a cross-platform app
- Mobile-styled website
- Hybrid apps
- Cross-compiled native apps
- MBaas and remote services
- Organizational concerns
- Key takeaways
- About Rich Morrow
Today’s developers now have several choices to assist with cross-platform design, ranging from options of application type, supported languages, toolkits, and delegation of logic to scalable, remote backends. Each of these comes with a set of trade-offs, and the speed with which they evolve requires examination of where each will be headed in the future.
In this report, we explore and expand on the following:
- The four avenues through which mobile cross-platform development can be achieved (mobile-styled web app, hybrid app, cross-compiled app, and MBaaS), along with the limitations, benefits, and use cases for each.
- The tremendous upside of solutions like Xamarin and Appcelerator, which enable developers to write code in one language and cross-compile down to native code on mobile devices.
- The fairly recent trend in offloading client-side business logic to MBaaS and remote service solutions and where this approach does and does not make sense.
- Organizational and structural challenges encountered by web and desktop development teams and how managers can best overcome those challenges.
(Feature image courtesy Flickr userphilcampbell)