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.
-
-
Replying to @wycats @slightlylate and
The Web as a platform lost on mobile. We can help parts of it remain relevant. Especially JavaScript
1 reply 0 retweets 0 likes -
Replying to @andreasgal @wycats and
I (obviously) think it isn't totally lost; but very much losing.
2 replies 0 retweets 5 likes -
Replying to @slightlylate @andreasgal and
BTW, the way to rebuild is from product/market fit, and *that* means responsible amounts of script because most addressable market is EM.
1 reply 0 retweets 0 likes -
-
Replying to @andreasgal @wycats and
...sigh because it never embraced the actual web and kept making the same mistakes we did with Chrome Apps despite a better offer? Or some other reason?
3 replies 0 retweets 3 likes -
Replying to @slightlylate @andreasgal and
That's the reason I sigh :smile: I remember asking about packaged apps in the first Chrome Dev Summit. You told me they weren't the future, but Chrome would have to circle back around. Chrome leadership and FF leadership, on the other hand, were in love with packaged apps.
1 reply 0 retweets 2 likes -
Replying to @wycats @slightlylate and
Packed apps were a hack because app cache was so horrible. It was a quick fix.
@fabricedesre hacked it in a day or two. Took years to get the real thing in place. We had to ship so some day we can do the right thing. That day never came3 replies 0 retweets 0 likes -
Replying to @andreasgal @slightlylate and
If you ship a crappier native experience, you'll get canned before you can do the right thing. Because of a desire to ship fast, FFOS didn't have any vision other than "native, but worse". Again, don't want to armchair quarterback, but this vision didn't sell.
1 reply 0 retweets 4 likes -
Replying to @wycats @andreasgal and
You are totally wrong on the reason for the lack of success of FFOS. Rather, look at what makes or break a mobile platform: official support from top apps.
4 replies 0 retweets 4 likes
Top apps need a reason to support a platform. At the time, nobody wanted another, crappier platform. Apps rejected FFOS *and* Windows Phone. But ~PWA had a major advantage. You could pitch apps on building web and native apps at the same time.
-
-
Replying to @wycats @fabricedesre and
TLDR I don't disagree at all that support from top apps is a prerequisite for a successful platform but that's circular. You need to give them some reason to add another app to the matrix, and "help birth another, crappier platform into the world" ain't it.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.