I am developing an app where there is a WebView that will be viewed a lot. The people telling me what to do therefore wants the website to load when the app starts, so that it will be ready when the user decides to open the page with the WebView.
One of my ideas were to use a Future<http.Response>, as described Here, but I don't think that will work since WebView expects a string as initialUrl.
Do you have any ideas on how I can achieve this?
Thanks!
Related
I don't like how my Android WebView app displays on some devices, so when I found out that crosswalk-project could fix that, I went to crosswalk-project.org but the website was down. Is there a way around it or an alternative to it?
Or will using WebChromeClient instead of WebViewClient fix it?
I want my WebView app to display the same across all devices and the Javascript "share" feature in one of the web pages of the website should work.
I made a HTML5 game for web browsers. Some of the players asked me if I could make it available as an App. Now I have a developer key, but just a VERY basic knowledge of Xcode / objective-c and I dont actually own an Apple computer. (But I can run Leopard/Xcode in VMWare).
Is it very bad practice to make a storyboard application that basically consists out of a splashscreen and a webview that loads my html game page with some added js/css to match the resolution?
Will Apple allow a game developed like this? It seems way easier to update etc...
Can I remove the bottom status bar from a webview using the meta tag? Or does that just work in safari, and will localstorage work?
Are there other, better, faster ways to port html5 to an app?
Sorry for the huge amount of questions, but I couldnt find satisfactory answers to all my questions, and I guess more people will have the same...
gr
Let me try to help you:
No, its not a "bad practice", but maybe for your app it's simple to do just a normal Single View Application. It doesn't mean that it's going to be wrong doing a storyboard, it;s just simpler.
Your App is only going to open a WebView with an URL, so, if you dont do anything weird, it's not going to be rejected.
If you are talking to the status bar, yes, it's possible to remove it easily.
I think that's the best way, just open a view with a webview on it. Another way is making your app call Safari with that URL, that's up to you (your app will go to the background and Safari will be called)
And an extra one: Its totally ok doing it with VMWare, I develop like that sometimes with my PC ;)
I'm creating a Mobile App with JQM and JSP I'm using Bookmark bubble to do this, but I just want to ensure I understand what is happening behind the scenes here.
Is the static HTML generated by my JSP saved locally on the iPhone?
Does clicking on the APP always get fresh info from my online server or does it cache?
I'm assuming it still uses Safari to render? And just hides the toolbar etc?
If instead of hosting this online, I packaged it as an Apple App and it went on App store,
would the device still use safari to render it?
Thanks!
Documentation is at: https://developer.apple.com/library/content/documentation/iPhone/Conceptual/SafariJSDatabaseGuide/OfflineApplicationCache/OfflineApplicationCache.html
It's possible to cache the page(s) locally.
Is it possible to open another app, like Camera, from a third-party app? I know there are URL schemes - http://wiki.akosma.com/IPhone_URL_Schemes - but I just want to open an app, not send any data to the app.
Unfortunately, no. Launch Services is private API on the iPhone. You application can launch another app only through trying to open a URL registered by that app or a file document the app understands. However, as far as I know, your app has no control over or knowledge about which app exactly will handle the URL or the file.
One way to fire up the camera from within your app, of course, is the UIImagePickerController class.
http://developer.apple.com/iphone/library/documentation/uikit/reference/UIImagePickerController_Class/UIImagePickerController/UIImagePickerController.html
It's not quite what you're asking, but it might be as close as you're going to get.
I have a couple of html links attached to buttons in my app.
I'm just wondering whats the best practice for following a html link in an iphone app.
I'm not sure if the app should exit and open safari or if a web container should be used etc.
There's no real best practice, it's whatever you think your users would appreciate. Some apps offer the best of both worlds, by putting a UIWebView in their app to view web content and then a button to open the same page in Safari.