Devoxx 2015: Angular FTW?

Imagine, you're a developer in a big company. Imagine, your boss gave you the technical leadership of the next web project and the freedom to choose whatever technology you want. "Great! Thats my chance to finally do something with AngularJS". But does Angular fit your needs? Does it make sense? Is it the grail you always looked forward to? Lets see some examples, hear some stories and learn why the answer is no.

Transcript

1. Angular FTW? DEVOXX 2015
2. Roman @rstrangh
3. Sebastian @sebbe128
4. innoQ https://www.innoq.com
5. Angular FTW? disclaimer
6. http://de.urbandictionary.com/define.php?term=FTW
7. http://de.urbandictionary.com/define.php?term=FTW
8. Imagine this…
9. You’re a kickass developer.
10. You and your team have to build a web application.
11. Could be a brand new one.
12. Or one next to others.
13. You’re interested in Angular – should you use it?
14. Dude, it’s 2015. This is the way you do 
 web development 
 these days. ”
15. I always wanted to check this out. ”
16. Sorry, management said we have to do it like this. ”
17. Google built that, it must be awesome. ”
18. © Matthew Black https://flic.kr/p/YFYnd What could possibly go wrong?
19. Well, chances are…
20. © Daisuke Tashiro https://flic.kr/p/jimnqH You don’t make it on time.
21. © Alex Alex https://flic.kr/p/uAbxzu You don’t make it on budget.
22. We all know what happens next…
23. http://gfycat.com/UnfortunateSimpleBilby
24. Let’s fix this.
25. Things to consider before choosing a web framework…
26. Users Productivity Architecture Organization
27. Organization
28. Some constraints to keep in mind…
29. Time
30. Budget
31. Technology © Luca Boldrini https://flic.kr/p/8nSrrb
32. Team © Defence Images https://flic.kr/p/fH4AAt
33. Always know your business model.
34. Users
35. Knowing your users always helps.
36. © Valarie Apperson https://flic.kr/p/5yBiX1
37. They probably expect fast UI feedback.
38. UI Feedback © By U.S. Navy photo by Mass Communication Specialist 3rd Class Sarah West, Wikimedia Commons © Rafa Torres https://medium.com/@RafaTorres/psicodelia-in-material-design-animations-89555c264238
39. Maybe even offline usage.
40. Think about their contexts.
41. In what situations could users interact with your application?
42. What forms of input do they use?
43. What devices do they use?
44. https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889
45. What connection quality could be expected in these situations?
46. © Anthony Humphreys/Thrillist https://www.thrillist.com/recipe/nation/new-takes-on-pulled-pork-sandwich
47. And what about their intent?
48. What is their typical point of entry?
50. How long do they stay?
51. How about the time to first render?
52. https://www.virginamerica.com/
53. If your business model depends on lots of users, you should care about reach.
54. You can gain reach with…
55. https://github.com/alrra/browser-logos 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 2 3 3.5 3.6 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 5.5 6 7 8 9 10 11 9.5-9.6 10.0-10.1 10.5 10.6 11 11.1 11.5 11.6 12 12.1 15 16 17 18 19 20 21 22 23 24 25 3.1 3.2 4 5 5.1 6 6.1 7 7.1 8 9 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 + MOBILE Compatibility 26 27 28 29 30 31 32
56. © Jody Frost https://flic.kr/p/9JAbJN Robustness
57. © Yahoo! Accessibility Lab https://flic.kr/p/ax2JmR Accessibility
58. by Ana Tudor http://codepen.io/thebabydino/pen/RNEEZP
59. by Ana Tudor http://codepen.io/thebabydino/pen/RNEEZP
60. Search Engine Optimization
61. http://www.forbes.com/sites/innovatorsdna/2015/08/19/how-we-rank-the-worlds-most-innovative-companies-2015/
62. https://prerender.io/
63. Productivity
64. Can I get up to speed quickly with good documentation & tutorials?
66. Can I cope with the given programming model?
67. © Jonathan Khoo https://flic.kr/p/3WAaR
68. © CERN ATLAS https://cds.cern.ch
69. Can you expect help from an active community?
71. Can I use a wide range of mature components & plugins?
72. © Windell Oskay https://flic.kr/p/4hABNH
73. Can I validate assumptions with rapid prototypes?
74. © Rosenfeld Media https://flic.kr/p/74xRbU
75. Architecture
76. Do I need a certain degree of stability?
77. Example: Wire Transfer
78. Example: Wire Transfer ?
79. Can I handle dependency management?
81. © Ben https://flic.kr/p/5bq6XE
82. Do I have to integrate other applications?
83. © Ben https://flic.kr/p/5bq6XE
84. Is it OK to create a monolith?
85. © hint of plum https://flic.kr/p/epubbg
86. Can I still expect scalability problems?
87. Yes, you can. But it depends.
88. Wrapping things up.
89. Know your business.
90. Ask the right questions.
91. Compare your options.
92. Make sane trade-offs. Ist das nicht sehr ähnlich zu “Compare your trade-offs.”?
93. Decide as a team.
94. Angular FTW? Maybe.
95. Thank you.
96. Questions? Roman Stranghöner roman.stranghoener@innoq.com @rstrangh Sebastian Janzen sebastian.janzen@innoq.com @sebbe128