61–70 of 78 posts
Related (add bookmarks to home screen):
http://lifehacker.com/5809338/add-web-site-bookmarks-to-your...
I tried this with a site of mine. GoNative works great and there's a lot of future potential too. However, at a certain point, we're just re-mapping the WWW sites 1-to-1 to wrapper apps. Regardless, I place the blame for this on users, entrepreneurs, and consultants, and I think GoNative is really just giving everyone what they want (for better or worse). Related (add bookmarks to home screen): http://lifehacker.com/…
Earlier quoted context omitted.
Out of curiosity, how hard is it to build something that could parse HTML markup and some CSS stylings and convert that into native views? Assume that the HTML markup and CSS is all done as per your documentation, so that the parser works as expected every time.
As @nkozyra says, understanding what all the links do is hard, however there are automated ways of converting common types of webpage layouts into structure data for native presentation. For example, our startup (shameless plug) utilizes a computer vision technology to automatically extract structured data from articles, images, products, and videos, etc: http://diffbot.com/products/automatic/ . These can then be use…
Minor note of little importance: 'Features > Performance > "abandonned" ' is a misspelling.
Apple have a rule against making apps that "are simply websites bundled as apps". You should probably mention that somewhere on the website to avoid having a bunch of people pay for a developer account only to get their generated application rejected by Apple.
There are tons of web-view based apps in the App stores. Phonegap bases their entire business on a similar concept.
(I spent some time playing with Phonegap but it was two years ago and a simple app took 30 seconds to launch on an iPhone 3GS. Probably significantly better now, and faster as hardware has improved.)
I tried this with a site of mine. GoNative works great and there's a lot of future potential too. However, at a certain point, we're just re-mapping the WWW sites 1-to-1 to wrapper apps. Regardless, I place the blame for this on users, entrepreneurs, and consultants, and I think GoNative is really just giving everyone what they want (for better or worse). Related (add bookmarks to home screen): http://lifehacker.com/…
Blame the users and Apple. Users for thinking for some reason an app is automatically superior. Apple for having no incentive to make users think otherwise. It greatly annoyed me how apple let their webapps directory rot until they finally removed it. For those that don't remember, webapps were the only apps when the iPhone first came out.
Does it make an actual native app or just a wrapper around a web view? I have a couple of (Android) apps that I use that are clearly just a wrapper and it's really annoying. 1) The back button always exits the app instead of going back a screen as would be expected. 2) Switching to another app and coming back causes the app to reload rather than staying on the screen it was on when I switched out.
The only reason you are being bitten by those two points is because the developer is being lazy and neglectful of user experience. Making those two issues dissappear takes about 6 hours of developer time.
Does it make an actual native app or just a wrapper around a web view? I have a couple of (Android) apps that I use that are clearly just a wrapper and it's really annoying. 1) The back button always exits the app instead of going back a screen as would be expected. 2) Switching to another app and coming back causes the app to reload rather than staying on the screen it was on when I switched out.
Apparently the version numbers are not being increased for each successive build, and you really need to do this. Why? Because I can't even update my app by editing the source code, changing the version number (which is already kinda annoying to have to do) and uploading the new apk release due to it not being signed with the same certificate you guys use....
Does it make an actual native app or just a wrapper around a web view? I have a couple of (Android) apps that I use that are clearly just a wrapper and it's really annoying. 1) The back button always exits the app instead of going back a screen as would be expected. 2) Switching to another app and coming back causes the app to reload rather than staying on the screen it was on when I switched out.
Nice work, but there is a huge problem and I really hope you fix it ASAP or else I'm SOL for updating the app I just released with this. Apparently the version numbers are not being increased for each successive build, and you really need to do this. Why? Because I can't even update my app by editing the source code, changing the version number (which is already kinda annoying to have to do) and uploading the new apk…