...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?
-
-
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 -
Replying to @fabricedesre @wycats and
I enthusiastically owned the FireFox Phone with FFOS and for a little while, when my Samsung Galaxy S4 died, I limped to end of my AT&T contract on it. Terrible experience mainly since the Google Maps and Twitter ports sucked beyond all comprehension.
1 reply 0 retweets 0 likes -
Replying to @kevvurs @fabricedesre and
Gmaps: we were getting the 'basic' version because the full version was chrome only and had js errors on other platforms (same for Gmail). Twitter had a basic Web version, not so bad but not as good as the desktop webapp.
1 reply 0 retweets 1 like -
Replying to @jwajsberg @kevvurs and
Were you getting the basic version on desktop firefox? Twitter was an enthusiastic early adopter of service worker, so perhaps teaming up with them would have helped? Did you talk to the Chrome team about what would need to be standardized for GMaps?
2 replies 0 retweets 2 likes -
We got a better GMaps towards the end of FxOS (never a better GMail though). Twitter Lite was working in Chrome only at the time. FxOS never got Service Worker (it was in the work when we stopped FxOS) and appcache performance was bad.
4 replies 0 retweets 1 like -
Replying to @jwajsberg @kevvurs and
I was hoping for more leadership from Firefox on SW, rather than waiting for pro-stds folks inside of Google to win, then belatedly think about implementing. Firefox had such a great opportunity to show what an emerging markets, hosted-based phone OS would look like.
3 replies 0 retweets 0 likes
I genuinely am not trying to armchair quarterback on the details. I wasn't in the strategy room and don't know what that felt like. But I do know that I'm sad that all of the Web OSes of the era were copying the iOS/Android model, and there was an opportunity to do otherwise.
-
-
yeah, a lot of us developers were sad about this during all this time. Maybe we should have pushed more about it, but in the same time we had to ship something good with a lot of pressure from partners, and weren't that many people.
1 reply 0 retweets 2 likes -
Replying to @jwajsberg @kevvurs and
I know the feeling man. I don't envy your situation at the time.
0 replies 0 retweets 0 likes
End of conversation
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.