Earlier quoted context omitted.
fastbkapp will receive the following info: your public profile, friend list, email address, custom friends lists, messages, friend requests, News Feed, relationships, relationship interests, birthday, chat status, notes, work history, status updates, education history, events, groups, hometown, interests, current city, Photos, religious and political views, videos, website, personal description and likes and your fri…
So will the native facebook app. Of COURSE the fastbkapp will receive that info.
Poll: HTML 5 or Native mobile development ?
91–100 of 106 posts
Re: Poll: HTML 5 or Native mobile development ?
#92The question is not asking "What works?", but you're all giving that kind of answer. Is it possible to ask indeed what this question is asking? Can we detach the "I need to launch YESTERDAY!" attitude from these types of questions?
[MOAR EDIT:] Add in the qualification to the BMW/Saturn analogy that you're planning a road trip.
[EDIT:] To emphasize, the question asks, "Which will you prefer..." rather than "Which do you prefer..." It seems like the OP is trying to sideline the "functionality of today" question, which frankly given the rapid rate of growth[0] and adoption altogether[1], "what works today", "APIs available today" is largely negligible.
Re: Poll: HTML 5 or Native mobile development ?
#93Re: Poll: HTML 5 or Native mobile development ?
#94Intestesting that the poll results (currently) only give a slight edge to native, but the comments are overwhelmingly pro-native. I can see two possible reasons for this: 1) Native developers are the more opinionated of the two. 2) People who actually have experience to communicate prefer native
3) nothing is stopping anyone from upvoting the two
Re: Poll: HTML 5 or Native mobile development ?
#95Earlier quoted context omitted.
The biggest downside I found with kivy is the amount of time it takes to launch the app as it has to set up the python environment et al. If that's improved with newer versions of kivy I might go back to see what it can do.
The other standard downside of kivy is the mandatory giant app footprint. Hello World is going to set you back 25mb on Android.
Re: Poll: HTML 5 or Native mobile development ?
#96Native, but with the use of C# (Xamarin / Mono). And I don't think native takes more time. Debugging is much easier with native apps (imho).
Re: Poll: HTML 5 or Native mobile development ?
#97Earlier quoted context omitted.
The biggest downside I found with kivy is the amount of time it takes to launch the app as it has to set up the python environment et al. If that's improved with newer versions of kivy I might go back to see what it can do.
The other standard downside of kivy is the mandatory giant app footprint. Hello World is going to set you back 25mb on Android.
It's certainly another downside of course, but to be clear to anyone reading the apks are much less than 25MB. And 25MB actually sounds like more than I'd expect even uncompressed, but I haven't looked at it much.
Re: Poll: HTML 5 or Native mobile development ?
#98HTML5 first, Native later. To make available more seamless "native" experience to the user.
Re: Poll: HTML 5 or Native mobile development ?
#99Not having much experience with developing native mobile apps, I can only say what a pain it is to develop non trivial HTML5 apps that need to support a wide array of browsers. Your initial euphoria of 'oh wow I could make this thing for [insert browser of you choice] in less than [x amount of time]' is quickly mitigated when you try it on other browsers. Different browsers _will_ vary greatly in performance for diff…
> Not having much experience with developing native mobile apps, I can only say what a pain it is to develop non trivial HTML5 apps that need to support a wide array of browsers Multiply that pain with 10x and now you know what it's like to develop native apps. (Disclaimer: Grass is always greener etc)
Re: Poll: HTML 5 or Native mobile development ?
#100HTML5. My (Meteor & D3-based) application is primarily aimed desktop browsers, and it already very nearly works out of the box on mobile -- there are a few D3 touch events that need to be revisited, and a new layout that is friendlier for smaller screens; otherwise we're done. We don't need to access low-level hardware, and the idea of doing Native re-implementations of Meteor's bidirectional data bindings or D3's fo…
Looks like a cool project! Is Elon Musk involved? :) http://www.podaris.com/
No Elon Musk involvement. Yet. :-)