So you’re ready to take the plunge and develop your next project in Angular 2. But, Angular 2 is just one piece of a larger puzzle.
A key question you must answer as you define your Angular 2 architecture, is “which component and styling libraries should be used? Here is list of choices that this post discusses (in alphabetic order). You may have wrestled with this question while using Angular 1. A key new feature of Angular 2 is the separation of the renderer from Angular.
Native developers will likely be resistant to hybrid, and if it ain’t broke, don’t fix it (it being your team’s productivity).
Mixing CSS libraries can be treacherous and bloating, although the new view encapsulation may make this more feasible (but it won’t address bloat).Naturally, you can also develop more than one presentation tier.For example, most likely you’ll choose to use one approach for mobile and a different library for web and tablet. Consider drop downs, radio buttons, modals, tabs, inputs, date pickers, buttons, and on and on…To increase your speed to market and manage costs, people are always looking for 3 party components (commercial or open source) to give some nice short cuts.Sometimes, you might find a perfect open source component, but it uses a different styling library.