Sorry if I sound too naive.
We intend to develop a native app using Phonegap and Sencha Touch. One of the requirements are to have a Sat Nav feature in where you could give a post code and it will guide you to there. However, I assume that feature is too costly to develop at it's own and would also mean we would be making a wheel of our own. The thought is and this is the actual question, if we could invoke Android's native Sat Nav (that comes built-in) from our app.
If anyone can help, I will be grateful, also if you guys have any other ideas, kindly suggest.
I don't think there's any way of doing this using the built in Google Maps application, and I'd avoid using it anyway (it doesn't have offline map storage, so if you drive into an area with no mobile coverage you lose navigation). But there are a couple of APIs you can purchase to do this kind of thing: http://www.copilotlive.com/uk/enterprise/ and http://www.sygic.com/en/business:buy-now both appear to be able to do what you want.
If you mean launching the Google Maps app with directions, look here
https://stackoverflow.com/q/2663565/984393
Basically you send a request in the form of an Intent for android to star the maps application.
Related
I don't know it is suitable place for this question or not, if this is not the right place please redirect me to the right one. i am asking this question after spending 3-4 days. Please be with me.
I have a web app/Mobile app(Android and iOS) something like small ERP application. We want audio calling feature for the application, we have been looking for days but didn't get a suitable solution.
Our Requirement is
Browser - Browser Calling,
App to browser,
App to App,
browser to app
we don't need internet to phone feature. Ultimately we are looking for a solution that will allow user to call directly without knowing the phone number.
In my research i came across WebRTC, but didn't understand the logic.
so if there is any way (library or something) (free/paid), any kind of information will be helpful (article/library/webpage/explanation). To give me a path to move forward with the research.
thanks.
Paid Library :
1) Zipper -- It has native sdk for mobile and Javascript sdk for mobile or web. https://www.zoiper.com/en/voip-sdk
2) ToxBox is also good library for voice call. https://tokbox.com/
Open Source :
Try Linphone- Its good for voice calling - they also provide sdk for Mobile and web.
https://www.linphone.org
Open Source
http://www.pjsip.org/ - SIP platform based
I have been playing around with PhoneGap for a little while, and getting it set up to work correctly with Google Drive API is proving to be far more difficult than setting up a website which does the same.
I am wondering if it would be more to my advantage to cease trying to make the full app work with phonegap, and instead use phonegap to access a hosted site.
Note that I do not wish to open the site in the default browser. The goal would be to make it appear to be an application (no borders, url, back button, etc), but have the web server handle everything behind the scenes.
I know PhoneGap has an In-App-Browser available. Is this something that is possible with it? Or does it only function for more limited use?
Thanks
You can definitely use a WebView for your app, which display the webpage but give you the ability to control the layout around it. Running a WebView instead of native code may cost some performance but it's doable.
The company I work for is exploring creating "an app" version of their online video delivery webapp. The webapp is HTML5 and streams video. Nothing too scary but a lot of the stuff is server-side authentication with third party video hosts, code that will never be in a mobile app for security reasons.
The webapp has a lovely mobile stylesheet that works fine. We want an app that:
Shows a quick splash screen (and even that's optional)
Load the existing mobile website (not include it within the app)
And have the ability to specify an icon, give it a name and then shove it in the relevant marketplaces. That should satisfy the marketing department and it means I stay in control of what the app actually does.
Yeah, it's possibly the laziest app development ever... But, what's the simplest way to generate something like this? I was imagining there might be something out there already where you feed it your starting URL, splash screen, icon and name and it hands you back a multi-platform app.
Note: I'm not looking for something to create an app that looks like the mobile website and I'm not looking to put the content of the mobile website inside the app, I essentially just want a browser that loads the real mobile site.
Have a look at https://www.shoutem.com/. They provide a service similar to what you seem to be looking for but they charge royally for it. Considering the extra features you can easily add with their service your marketing department might just smell profit from using it and may therefore happily sign it off with their well known satanic smile.
There are a number of websites which provide easy web app development for a website. One of the famous is App Maker . Others include:http://www.viziapps.com/ and http://ibuildapp.com/
Since posting this, I have found:
http://www.websitetoapp.net/create
Feed it a URL and an Icon and it'll give you an Android app. Pay $5 and they'll disable adverts. Seems like it might be perfect for the Android half of this project.
Now, is there anything out there that will do this for other platforms?
I was developing an Android app under the jQuery mobile framework using phoneGap technology. The app included Google maps.
The problem is, it is too slow .... really slow.. I tested it on several android devices and found the same issue everywhere.
I'd like for maps to run like they do on the native Android Google Maps (default). Is this a common issue using the mentioned framework, or perhaps something I'm doing wrong?
One thing you can do is fire an Intent to make the native Maps application take care of your mapping needs, if that works for you.
For example, if you want to show the user a map of a given address, you can fire a android.action.VIEW Intent, with a URI like:
geo:0,0?q=1234+foo+bar+qux+avenue
More info on available system intents:
http://developer.android.com/guide/appendix/g-app-intents.html
You should take a look at this:
https://github.com/phonegap/phonegap-plugins/tree/master/Android/WebIntent
I am planning to create an application in android which has following features
Show Source to Destination Route
Show Reverse Route
Show Traffic Data
Show alternate Route
Store user data
apart from that i want to use some android native controls such as image button , textbox , dialog over the map.
Now after reviewing this link i am bit confuse in choosing the approach among
Google Maps API V3 in the Browser
Google Maps API V3 in a Browser Embedded in a Native Application
Native Google Maps APIs
Can anyone please help me out in choosing the right approach ?
Well, there's no simple answer to that. Every approach has its pros and cons.
Now let me state few insights that might help you in your decision (based on the idea that you want the map as a part of a native android app, not just a html5 app - correct me if I'm wrong):
You need to store user data.
If you want to store the data in the app, then I guess you can leave out the first solution. It would be very difficult (or even impossible) for you to properly maintain your data with map in a browser. The best way to maintain data is then to directly communicate with a server from the webpage and store data on the server (so you need a server backend). You can also pass some data from the webpage to an activity by registering an intent filter for your own url schema.
You don't have such problems using approach 2 and 3, where you can use android code (if you are embedding the map in a webview you can access android code by binding javascript code to android code).
You want to use android native controls.
Now you can also leave out the 1st solution, you are using browser controls there. In the 2nd solution, you can use both (the map needn't fill the entire screen and you can also place controls over the webview).
Google Maps API v3 is frequently updated and currently much more comfortable than native API. Native API wasn't much updated (not sure if it was updated at all) since Android 1.6.
From these 3 points I would prefer embedding Google Maps API V3 in a webview. Of course, I might have missed some important features of your app.