New answers tagged

1

As Morons mentioned in their answer, it is very difficult to verify the entity at the other end of the connection. The simplest way to provide some level of authenticity is to have the server check some secret that that only the real entity would know. For a user that might be a username and password. For a piece of software where there is no user you ...


1

I would go this way: This uses a service to expose all of the bussiness functionality. Then, your MVC app could grab all the data returned from a service a create a View with it, while the API would use the same service to return JSON/XML. Your MVC app and you API would then have the same funcionality and you mobile app could grab whatever info is needed ...


0

In the case of a simple web application, you can completely share the codebases between the website and the mobile application. In this case, you basically just wrap your website code in the mobile application (Cordova does follow this way of thought). It makes sense to diverge the codebases in some cases, but I think that this is the exception to the rule, ...


2

I read quite a few forum topics and mailing list (link), the general answer was that if you are using the Android SDK, and you do not have an MP3 encoder/decoder in your application, then you don't need a license for your app. The MP3 license for playing is already provided by the device manufacturer. Also, basically everywhere else than the USA, MP3 ...


1

In the end, if I didn't misunderstand you, you've got the following situation: Android device has a clock set to a potentially random/wrong time. There's no network connection other when deploying them in their dock (probably during the night or in the morning). As such I assume the only unknown value is the time offset between the local device's clock ...


9

There's actually quite a bit you can do to recover something close to the actual time of most of your events. Android gives you a few useful tools to work with, notably broadcast intents sent when the device completes a boot, when the system clock changes and when a shutdown is imminent. It also gives you a way to check the amount of real time that's ...


1

A simple (but approximate) way to approach this is to record the offset of each device every time it syncs. When inserting the data into your master database, use the most recent offset value for the device to adjust the recorded time. Without a reliable reference clock on the device, it's not even possible to guarantee that two actions recorded by the ...



Top 50 recent answers are included