I want to be able to track a person through their mobile phone and
display those whereabouts on a website. I read some stuff here about Safari and iPhone.
What I need is a starting point in the sense of what is possible, and
if it is only possible for certain phones. I can ask a lot of specific questions as I've read bits and pieces everywhere, but what I need is a general layout of what needs to be done and, if possible some of the steps to accomplish it.
Thanks.
Well, if we assume you are starting from scratch, here is a high level list of things to figure out:
familiarise yourself with geolocation coordinates and the gps system. If you need to make sense of the raw location data, there is some math involved.
pick a location-aware mobile platform. Some phones will implement jsr-179, which is a JavaME API. In addition, you can get location data using python or C++ on Symbian phones. I suspect Android and iPhone both have their own location API.
figure out application deployment for the platform you picked. How does the mobile application get on the device? A phone manufacturer or network operator application store, a third party store like www.getjar.com, pre-installed on the phone via a partnership with the manufacturer or the network operator...plenty of options.
come up with a sensible way of packaging mobile location data and send it over the network to a remote server.
make a website to display the location data stored on the server.
Related
I'm planing to make android app the need of it is to recognize building in the city .
I need help in choose the most important unique features in the buildings ,such that the size of the features stay small as it will not be a practical application if the size of the database become large , is running the application offline possible or i should send the features to remote server for processing the similarity between the pictures ?
Actually, you could choose some simple but effective features(building logo, the foreground of the building) for recognizing offline.
In order to make the result more accuracy, you cound send the GPS information back to the server.
Do not only recognize the building by analyzing the picture, sometimes ,you can get more information from the Android.
Good luck.
I've made my app running on the Google Glass, but it's a little slow in real time. Is there a way to connect my Android phone with the Glass for data communication, so that the phone can take care of the calculation, and the Glass only show the result? The Glass can tether with Android phone by bluetooth, so it should be able to transmit data via it?
Don't know if it's possible to run my app on cloud server and send the result back to my Glass, but guessing that would be slow as well.
Any suggestion is more than welcome! thanks.
Yes, you can connect your Android phone with Glass for data communication, to receive internet content for example. This can be accomplished using Glass to WiFi (but you need the phone to set this up the first time), or Glass to phone to Bluetooth if your phone supports bluetooth tethering, which is often a carrier option.
If you are a Glass explorer this should have been explained when you picked up your Glass, but you can contact the Glass Guides for more information, if you are a Glass Explorer you will have this contact information. I have found them to be extremely helpful and fun to work with on usability questions. It doesn't hurt that if you visit them physically they ply you with treats and drinks.
If you are asking if you can open a socket directly between phone and Glass, that is not supported functionality, but you can request it. It might be possible when the GDK is made public, but there is no timeline for that.
If you wanted to do calculations on a phone and pass them to glass they would have to go through the cloud, as described here. Check out the section titled "How developers interact with Glass" and the accompanying graphic. I find it to be fast (sub one second with good connectivity), but that is subjective, your speed needs are not well defined in your question. A consideration is that every round trip of data will count against your API console daily limit, which is 1000 for most everyone. There is also a 10 request/second limitation.
Last note - there are unsupported ways of talking directly between Glass and a phone for a device you have direct access to, but this is not supported, and could not be used by other Glass users very easily. The techniques to accomplish this are alluded to in the Google I/O 2013 session: Voiding Your Warranty: Hacking Glass.
This forum isn't an appropriate one to discuss this, if you were to contact me directly somehow I could give you some pointers in the right direction, but I don't advise this route at all.
I am currently creating a quiz application, which will send data between two different applications on the iPad. Is there a way to connect two Flash CS6 applications together via a local database? These flash applications will be used on iPads.
It is very important that the information is not accessible online.
As I recall iOS is very much sand-boxed to where you can't share a local database between 2 Apps.
You could look into assigning your apps different URL prefixes / schemes, but I am unsure how well Flash supports setting those up. If you get it to work though, then you could theoretically maintain one local database per app and communicate between the apps using the URL prefixes. Of course maintaining and syncing 2 separate database may turn out to a pain.
Really the solution I would lean toward is to store the common database on a server that does not have a front end to it, just a simple API. This would prevent users from accessing the data online while allowing any number of apps to access it at will. If you ever expand into Android or other mobile platforms this would allow the same data to be readily sharable as well.
I am an Android developer. I haven't developed J2ME applications before. I have a requirement in which the client needs a J2ME application which requires me to store around 10,000 (Each record would have around 60-150 KB of data) records on the mobile phone. The mobile app will also be tied up with a backend server using a REST based web service.
The client wants the app to run on a specific mobile - Nokia 5233.
I need the correct options to proceed. Currently I am using the RMS and LWUIT. I chose them because:
RMS - I am using the CLDC profile. I am not aware of any DB that can be used with this configuration. Apache Derby is supported only in CDC.
LWUIT - There are many cases in the application where the TextField requires event listeners, the StringItem in LCDUI doesn't seem to have any event listeners.
Please enlighten me. I'm not sure whether I am taking the right direction.
RMS is probably your only decent option for on-device data persistence in J2ME (unless you go for direct file access using JSR-75, however if you aren't signed, the user will see all sorts of intrusive error popups when using this API). 10,000 records at 60KB per record, i.e. 614MB minimum? I've never heard of a MIDlet storing this size of data, RMS is intended really for a meg or two at most.
Why do you need to use J2ME? The 5233 is a Symbian^1 device, maybe try a native technology such as Qt? Probably far more reliable for that size of data, and easier to get a nice UI too.
(By the way, what events would you expect StringItem to give? It's a display-only widget.)
I'm trying to build a mobile application on a client-server model where clients are people's mobile devices and the server is a PC - all connecting over bluetooth.
I'm expecting the client to be very thin - just enough to establish communications, display some text, and relay user input.
What's the best framework to develop in? I want the maximum possible device compatibility (so for example not just series 60 capabale devices) as opposed to cool features - but the ability to scale easily to colour devices or ones with higher dispaly resolutions would be nice.
In the current mobile space, largest installed base + limited functionality = use JavaME. See http://java.sun.com and the the stackoverflow j2me and javame tags.
Easiest way might be to write MIDP application that uses Bluetooth API. That covers widest range of devices with least effort.