|fastbook response on hacks?||Luke Crouch||12/17/12 8:07 AM|
seems like a story set to explode. But it needs a response/reminder that
HTML5 is more than just Webkit.
Fastbook doesn't work on Firefox OS, Firefox Mobile, nor Opera Mobile. I
wasn't able to check Windows Phone.
|Re: fastbook response on hacks?||John Karahalis||12/17/12 8:56 AM|
Very, very cool.
I would also love to see us engage with them. Wondering what Robert N. thinks...
----- Original Message -----
> From: "Luke Crouch" <lcr...@mozilla.com>
> To: "engagement-developers" <engagement...@lists.mozilla.org>
> Sent: Monday, December 17, 2012 11:07:41 AM
> Subject: fastbook response on hacks?
> engagement-developers mailing list
|Re: fastbook response on hacks?||Christian Heilmann||12/17/12 8:58 AM|
How is them using the HTML5 brand to promote more webkit only solutions that aren't even tested in a webview very very cool?
|Re: fastbook response on hacks?||John Karahalis||12/17/12 9:03 AM|
Just speaking to their goal of proving -- in code -- that the open Web can be just as powerful as native applications. This could be much more powerful than any blog post correcting Zuckerberg.
Their choice to target WebKit only is obviously a problem, but one more reason to start a conversation with them.
> From: "Christian Heilmann" <chei...@mozilla.com>
> To: "John Karahalis" <jkara...@mozilla.com>
> Cc: "engagement-developers"
> <engagement...@lists.mozilla.org>, "Luke Crouch"
> Sent: Monday, December 17, 2012 11:58:52 AM
|Re: fastbook response on hacks?||Christian Heilmann||12/17/12 9:10 AM|
We have conversations with them. most ended with "people use iPads, we concentrate on those". This is very aggressive marketing for their platform mostly. Much like the last post about their app wrapper: https://www.sencha.com/blog/creating-native-applications-with-sencha-desktop-packager/
Sounds awesome, open and driving HTML5, right? Until you do the math as in the first comment:
Desktop packager sounds great, but, only being available w/ Sencha Complete: Team, which is $2,195 per seat with 10 seat minimum puts it at $21,950 to use it… Seems awfully steep.
That said, it will be interesting to see the story unfold, let me check if they are up for an interview or some guest post.
To: "Christian Heilmann" <chei...@mozilla.com>
|Re: fastbook response on hacks?||Luke Crouch||12/17/12 9:10 AM|
I think on the whole spectrum, HTML5 > WebKit > Native.
I'll admit I started this thread hoping to provoke Christian to write a
blog post response about "webkit-only solutions that aren't even tested
in a webview" :)
|Re: fastbook response on hacks?||Christian Heilmann||12/17/12 9:16 AM|
|Re: fastbook response on hacks?||Christian Heilmann||12/17/12 10:08 AM|
|Re: fastbook response on hacks?||Robert Nyman||12/17/12 2:25 PM|
I made a little noise about this early in the the day since I think it was an important thing:
The reason is that with Facebook first moving to native on iOS and now Android, I believe it's very important to show that HTML5 can do it. Sure, it was webkit-only here, but that was of minor importance. It was a proof of concept and a way to get attention for Sencha - and used in the best manner, we can hopefully sway this into something good for the web, open technologies and Mozilla/Firefox.
After my tweet I was in a lot of discussions about it, and also with Sencha developer Robert Dougan (@rdougan).
One thing that I said to him - and that would be interesting to see - is to compare Facebook's current mobile web version and Sencha's implementation, analyze pros and cons and see how both of them could benefit from each other.
I think that would be the best starting point, and if/when more discussions have been had and it works in more web browsers than WebKit, then we could talk about it on Mozilla Hacks.
|Re: fastbook response on hacks?||Gervase Markham||12/18/12 6:14 AM|
On 17/12/12 22:25, Robert Nyman wrote:Well, yes and no. IMO, the "we can do it while Facebook can't" thing is
only valid if they take on the same challenge that Facebook took on. And
that includes multi-browser support - doesn't it?
|Re: fastbook response on hacks?||Robert Nyman||12/18/12 10:53 AM|
> Well, yes and no. IMO, the "we can do it while Facebook can't" thing is only valid if they take on the same challenge that Facebook took on. And that includes multi-browser support - doesn't it?No. Facebook mobile web is something different. This was compared to Facebook building webkit-only in WebViews on iOS respectively Android.
One of the problems overlooked here, though, is that Sencha did it in mobile web browsers, and part of the problem lies in, for example, iOS behavior in WebViews compared to the mobile browser.
So, not a 1:1 comparison, but at the same time, not something finished either. A good first step that hopefully leads to multiple web browser support, and that's a discussion to be had with them.
|Re: fastbook response on hacks?||Luke Crouch||12/18/12 12:30 PM|
On 12/18/12 12:53 PM, Robert Nyman wrote:WebViews are a big problem, and it shows developers that we should drop
this whole PhoneGap/App nonsense and go (back) to mobile web at simple
PhoneGap is just that - a stop-gap. What's the point of wrapping your
HTML5 in PhoneGap considering 1. iOS and Android WebView hobble your
app's performance 2. the iOS and Android stores absolutely *suck* for
The latter point is made almost comical by stuff like
spent 5 minutes trying to get that crap to work. Why not just have a
card with incrediblepizza.com on it that does all that BS for me?
Or my personal favorite is a local highway billboard that says
"Available in the App store! Go to <url> for details." The whole app
packaging, distribution, and discover-ability situation is such a mess
that they send users to the web anyway.
IMO we should be hammering native apps on this BS, and it's probably
time to start moving away from the whole PhoneGap/Appcelerator approach
too. Mobile support for HTML5 is starting to catch up to the native
API's those libraries give dev's anyway.
|Re: fastbook response on hacks?||Robert Nyman||12/19/12 12:34 AM|
> IMO we should be hammering native apps on this BS, and it's probably time to start moving away from the whole PhoneGap/Appcelerator approach too. Mobile support for HTML5 is starting to catch up to the native API's those libraries give dev's anyway.I think we're getting there, but we're not there yet. It will be interesting to see if Apple etc get their WebViews together first, or if mobile web browsers will have enough capability rendering WebViews more or less useless for most scenarios.
|Re: fastbook response on hacks?||Luke Crouch||12/20/12 9:35 AM|
On 12/19/12 2:34 AM, Robert Nyman wrote:If I could wave a magic wand to control mobile platform vendors, I'd
make them work on their mobile browsers rather than their WebView
I'm probably just building too-simple mobile apps to need all the API's,
but API support isn't even the main problem with WebViews - performance
and distribution/discovery is crap.