As I start writing down this post, I know it will be fairly short: I have just a couple things to say, and one can only add a finite number of fillers to lengthen a couple concepts.
Consider yourself warned :)
Evidence A: Web Components
If you don’t know what Web Components are, please take a quick detour to this nice and rather hands-on introduction at CssTricks.com.
But - Hey! – I’m here to help, so here’s a definition of Web Components straight from that introduction:
Web Components are the future of the web, and we are starting to get there (see the next evidence).
Evidence B: Google Chrome
Chrome 36 was the first web browser shipping with a stable implementation of all 4 specifications of which Web Components are composed of.
Opera has since joined the ball, and Firefox is also improving.
Evidence C: AngularJS
- Angular is maintained by Google and the community.
- Angular 2.0 will force us developers to refactor our code and rethink our approach to the problems we try to solve.
Things will be removed, things will be changed and transformed.
The result will be something very very similar to a developer using Web Components to build their app.
Google is shaping the future of the web with Chrome and Angular.
That’s why I’m betting on Angular, and I think you should too.
Evidence D: Ionic
Ionic is a front-end SDK for developing hybrid mobile apps with HTML5.
And there’s Angular at its core.
Evidence E: Material design and ngMaterial
Material design is the new design philosophy and visual language by Google.
ngMaterial – or, Angular Material – is the official Material design reference implementation.
It is supported internally at Google by the Angular.js, Material Design UX and other product teams.
Also, main contributors of ngMaterial by Google are Ionic devs.
Ionic is here to stay, its peak is far away, and it will grow in prominence over the next couple years.
That’s why I’m betting on Angular and Ionic, and I think you should too.
- Yes, Angular is not technically perfect.
- Yes, hybrid apps (see Ionic) can’t technically compete with native apps.
- Yes, Google is technically != the web
- Starting to technically see a pattern here?
All you technical points are good. Maybe they’re even perfect.
Because strategy and alliances are how you win a war, not your technical level.Comments