Nicolas

Our whole team has been working towards this for about a year. But some special thanks go to @CharlieCroom and @jbell!

And no, we didn't take Twitter down :)

Answering a few questions about this…

This JavaScript stack has been in production for 9 months, powering the logged-in mobile web app.

For the last 2 years, the stack serving logged-out mobile web has been Scala, Google Closure Templates, and a sprinkling of JavaScript.

A few months ago @CharlieCroom started an experiment to move a fraction of the logged-out traffic over to the JavaScript stack.

This week and last, @jbell (our team's Node.js tsar) moved the rest of the logged-out traffic from the Scala app to the JavaScript app.

Seems like a good time to thank the webpack team again for their work and helphttps://mobile.twitter.com/TheLarkInn/status/829162214196117504 …

As well as the @GoogleChrome team. We're excited about the future of web apps on Androidhttps://mobile.twitter.com/addyosmani/status/829155355800145920 …

And Facebook engineering! In addition to React we depend on Babel, Yarn, Jest, and Redux.

@necolas It's great! I like it better than the mobile app now. Awesome work :)

@necolas I wish it hid the Safari UI when you add it to your homescreen though. I want to use it more like a normal app

@thejameskyle We found Safari's add-to-home-screen to be a bit broken. I wish that platform were kinder to web apps.

@necolas Really? In what ways?

@thejameskyle @necolas its horribly broken when you want to visit a link "outside" of the web app, which presumably is something users do

@thejameskyle @necolas so cumbersome. The other thing that's an ongoing issue is AV concerns -- audio, video work strangely in this context

@jeffehobbs @necolas External linking to Safari seems to work the way I'd expect it to