I’ve an "MVP" application that I'm developing using angular framework; as I have a solid understanding of this framework, so I will be able to create the MVP pretty fast. However, if MVP gets traction, I’ll be developing a larger application based on it, and by that time Angular 2 could be production ready.
I want to know the conventions, if any, that you would follow to make sure that the migration to Angular 2 from Angular doesn't turn to hell.
Angular2 is less complex than Angular1 in my opinion - when you learn Angular2, forget everything you've learned in Angular1, it's a very different framework.
I suggest just going Angular2 and not looking back. Now with the split in the AngularTS and AngularDart teams, if you find any bugs, it's much easier to contribute and provide a fix yourself.
Jan Vladimir Mostert
Idea Incubator
With the angular 1.5 and the components all it's so easy to migrate to angular 2, you can write the app in typescript if you want and make the migration easier :)
Angular = overengineered marketing hell already.
Use vanilla JavaScript/ES6 with some libraries and you will never ever in you life ask similar question again.
Theresa
Front End Web Developer (JS/HTML/CSS @ JAVA) : Predict the future by inventing it
With angular 1 you could still build an app from scratch. The complexity introduced with angular 2 nearly completely put me off angular, if I was not invited at the time to work on an a2 proj that was already established. Just build your app in 2 and don't look back.