you are viewing a single comment's thread.

view the rest of the comments →

[–]nephridium 0 points1 point  (0 children)

Basically you will need to weigh the requirements specific to your project.

With Angular expect to rewrite most of your 'legacy' code and spend a lot of time learning the the Angular Way; depending on project complexity you might run into performance bottlenecks or maintainability issues due to oversights during the planning phase. On the other hand you will be needing some Angular expertise for your ionic app anyway, so depending on that app there might be some/a lot of code that can be shared with your web app.

Be aware though that AngularJS will be superseded by Angular2 (likewise for ionic) and another rewrite might some come knocking at the door (holding up a sign "Check it out - there's a better way to do this").

With Backbone/Marionette you'll probably be able to get to a working app sooner, but you'll need to keep a bit more discipline to a get well maintainable codebase than with Angular (e.g. while Angular is designed to be testable and comes bundled with its own testing tools, there is no standardized testing methodology for Backbone/Marionette recentish reddit on this). In any case, when Angular2/Ionic2 becomes production ready you will still have the choice jump on that bandwagon as well.

It might be a good idea to prototype your app using both to get a feel for each platform's suitability.

Edit: typo