mwillmott

Blaze | London, UK | Front End & Mobile Engineer | Full Time, Onsite

Working with some of the largest urban transportation organisations in the world, we are combining our expertise in creating innovative hardware with our vision to change the way people move around cities. We’re building a new team to lead the development of mobile and web products that will be used by cyclists, transport providers and fleet operators.

We are a small, fast paced engineering team, building connected devices and mobile applications that people rely on to move around cities. We work extensively on both the Native and Javascript side of React Native applications.

We're hiring mobile and web engineers to lead the development of a new product we'll be launching later in 2018!

Please contact [email protected] directly if you are interested! You can browse our careers page at: https://blaze.cc/careers/

I'm generally in favour of people releasing more frameworks and showing off work like this. We're not being forced to use it and at the very least it allows us to see and understand other peoples thinking and approaches to new concepts like Flux.

With Marty.js posted the other day (https://news.ycombinator.com/item?id=8923053) and, having spent a while looking at that, i'm interested to know if the motivations for creating the two are broadly the same? Are they taking similar approaches or are there fundamental (or subtle) differences? This is something i'm struggling to understand so would appreciate other input.