Thank you for an outstandingly helpful piece delivered with clearly hard-won clarity of thought, expression and purpose.<p>The diagrams you created to support the piece are gold.<p>While the project work done for my business sponsors is confined specifically to iOS, hence the browser version/capability, carrier, UI, and UX problem domains are thereby narrowed, your first principles, conclusions, observations, diagrams, and commentary with prescriptive guidance is superb -<p>I, and I'm sure many other readers feel the same, owe you a debt of gratitude for what is likely a watershed post and effort at explication, caution, and actionable guidance.<p>Sublime setup with Joe the Volcano reference!<p>Looking forward eagerly, and with a good dose of appropriate humility, to your next posts on the subject.<p>Best,
Adam Cassel
This is a great article. My knee jerk reaction was to be a bit defensive "but native development is a lot of work too!" And it is, great applications require a lot of work regardless of platform.<p>But the article isn't (explicitly at least) saying that web-based mobile applications necessarily require any more work than porting an application between multiple platforms, but it is saying that web-based mobile application development isn't just "crank out an app and it runs great everywhere" which is something a lot of proponents (among whom I count myself) certainly do argue.<p>As the article concludes, there are a great many number of considerations when selecting a platform, and the detail here highlights the many that exist for mobile development.<p>I really very deeply enjoyed this article.