Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Longer version, see below for the TL;DR

As a developer with a strong background in the development of "classic" web applications I have been thinking about mobile web application architectures. One question that I cannot really seem to answer is: why do you need a framework like Sencha Touch (maybe even jQuery mobile, although it seems way more lightweight)?

Let me elaborate on this: For me, mobile web apps seem highly similar to "classic" web apps with client side MVC. OK, you need to be extra careful when it comes to efficient DOM manipulations, transfer of (static) resources, offline support and a few more things, but apart from this, the only notable difference seems to be the user experience. Users are expecting typical mobile widgets that preferably behave like the native ones. For this reason, I am thinking that frameworks and libraries for client-side MVC, that are used for "classic" web apps, are also sufficient for mobile web apps and that the only necessary addition is a set of mobile-like widgets.

TL;DR

What is the value of frameworks for non-trivial mobile web applications (think enterprise-level with years of development...) over existing frameworks for "classic" (desktop) web application development? What about "classic" web application frameworks + mobile widget sets?

share|improve this question

closed as not constructive by Jim G., Glenn Nelson, World Engineer, gnat, Caleb Feb 20 '13 at 10:13

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer 1

There are two primary benefits to using a framework for any development project:

Reduction in time and effort
If you had to write everything from scratch, that would take you quite a bit of time, therefore costing more to do. Starting your project with a bunch of code already written is a great time/cost saver.

Tested, verified solution
Existing frameworks are used for a lot of applications by a lot of developers. Bugs are discovered and fixed, and security holes are patched. If you write everything yourself, you then have to deal with all those issues as they come up.

share|improve this answer
    
Maybe I was not clear enough: I did not mean to imply that you do not need any framework for a mobile project, I am just interested in the additional benefits of using something like Sencha Touch when you could also use another client-side MVC framework + a widget set. –  BenR Feb 20 '13 at 5:13
1  
Same/similar answer in that case, just more specific. The framework is designed to handle certain things you are likely to need/do. Rather than cobble your functionality together from one framework and several widgets, you can just work with one framework that's already pulled stuff together. Just makes things simpler. –  Jim Feb 20 '13 at 13:56

Not the answer you're looking for? Browse other questions tagged or ask your own question.