We *obviously* said no. Pressing on the reasons they wanted it, we got flimsy stuff back. This whole ecosystem is dirty af and each BigCo that crosses a line enables the next.
-
-
The trends are clear. Was 15% time-spent on mobile a few years back. Continuing to fall. Even if it were only stable, still very much losing.
-
Saw mobile web lose first hand
@Lyft
Instant Apps and something similar in next iOS will be like K.O. -
Fwiw did Lyft promote their mobile version the same way they promoted their native? I love the PWA.
End of conversation
New conversation -
-
-
The fact that it's a close call is embarrassing to web and something I strongly agree with both of you we should fix, and something Mozilla could be doing more to help with. Sadly, "packaged apps" confused Google and then Mozilla into years of wasted time.
-
Google/Chrome folks seem caught up now. Mozilla: honestly I don't even know how to tell.
-
The
@chrome team has understood for years that native is the enemy to fight. WebView wrappers like Focus don’t move the needle in this key battle. Also not sure that fight is still winnable though.@reactnative might be the future instead -
React Native is a category error in this conversation. Either we care about the web and want the web to win, or technologies like Java, Kotlin, Swift, Objective C, and yes, JS via things like React Native will win.
-
The Web as a platform lost on mobile. We can help parts of it remain relevant. Especially JavaScript
-
I (obviously) think it isn't totally lost; but very much losing.
-
BTW, the way to rebuild is from product/market fit, and *that* means responsible amounts of script because most addressable market is EM.
-
Firefox OS ... long sigh
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.