OW2con'14 - Nanoko, 2 years feedback, Ubidreams

For 2 year now, Ubidream's team was using Nanoko to develop every web and

  1. OW2 Consortium
    For 2 year now, Ubidream's team was using Nanoko to develop every web and
    Transcript Header:
    OW2con'14 - Nanoko, 2 years feedback, Ubidreams
    Transcript Body:
    • 1. Nanoko, 2 years worth of feedback Nicolas Rempulski CTO - Ubidreams Orange Labs - Issy les Moulineaux 6 / 11 / 2014
    • 2. Once upon a time … 2
    • 3. Nanoko Timeline 2012 2013 2014 2015 Ubidreams goes cross-platform 3
    • 4. Multi canal nightmare 4
    • 5. Develop once, deploy everywhere 5
    • 6. Cross-platform strategy Application core : Single Page Web App (HTML5 / Javascript / CSS3) Packaging Desktop : website Mobile : mobile website / native application (Cordova a.k.a. Phonegap) 6
    • 7. Nanoko Timeline 2012 2013 2014 2015 Nanoko active development 7
    • 8. Development Runtime Dependency management Satellite technologies Assets optimisation Code quality Packaging Project management => Code reusability Continuous integration Dependency injection Platform adaptation Environment adaptation Library / Framework agnostic Maven plugin : coffee-mill Javascript library : h-ubu 8
    • 9. Nanoko Timeline 2012 2013 2014 2015 Open source release OW2 project 9
    • 10. Nanoko Timeline 2012 2013 2014 2015 1.2 release 10
    • 11. Nanoko Timeline 2012 2013 2014 2015 OW2 con’2013 Innovation award 11
    • 12. Nanoko Timeline 2012 2013 2014 2015 1.3 release 12
    • 13. Feedback 13
    • 14. Nanoko @ Ubidreams 2+ years of use by 6 devs on ~20 projects Goals are met : code quality, project management, productivity, … Improvements : as needed internally, push upstream to open-source project later 14
    • 15. Going open-source Identification : Positionning yourself in the Web Tech sphere is hard Visibility : AngularJs, ReactJs, NodeJs, Grunt, Yeoman, Bower, … Investment : Managing the product & the community is heavily time consuming 15
    • 16. Dependency management Web libraries fast release pace leads to « loose » version control (@Bower) Libraries & framework didn't deploy on Nexus repositories (until WebJars) Frameworks often offers « boilerplate » instead of autonomous releases 16
    • 17. Dependency injection H-ubu : Implementation of « OSGI-like » service injection specification Collision with module pattern (requireJs, AMD / CommonJS modules, …) Service pattern not widely used in Javascript territories 17
    • 18. Build Process DevOps for Web App by Javascript dev means Javascript tools (Grunt, npm, Yeoman, …) Maven not well established in front-end world (low-hype) Web build process today use extensive declaration (ant-like) instead of conventions 18
    • 19. Sequel
    • 20. Nanoko’s future Nanoko is used in Wisdom-Framework web assets build process Importing client-side and server-side component in the same project Satellite technologies integration (focusing on code quality & reuse) Showcases with leader frameworks (AngularJs / Reactjs)
    • 21. The End Contacts : nrempulski@ubidreams.com Infos : http://www.nanoko.org http://www.ubidreams.com http://www.wisdom-framework.org
    View More