ads

lundi 14 septembre 2015

[Advice] Developing a 'kiosk' app - which watch / approach for a prototype?



Good evening - I'm a long time lurker at XDA and have gleaned a lot of useful information from this site, so thanks for that.

I have a client who is looking to build prototype for a device containing only one app, for a very young market, which will be the only app runnable on the device (think a smartwatch tamagotchi) - the priorities are that there's bluetooth, wifi and an accelerometer fully accessible to the app, and that the watch be relatively cheap. Now, while I've been a developer and sysadmin for a number of years, this is my first Android or wearable project, so I wanted to see if anyone had any useful tips on approaches to take, and devices to try for this prototype. (Also, I know the idea of locking down a device like this might be an anathema to people posting here. See this as an academic exercise in what's possible.)

As far as the approach goes, it seems to me I have a few options:

- Get a watch already running Android Wear, develop the app using Google's APIs and see if I can the modify the OS to boot into a single app.
- Get a (probably cheaper) watch which I can then flash with a ROM built by someone else, but will still allow me to access the accelerometer, then lock this down
- As above, but build my own ROM, containing only my app.

As far as devices go, we've had a look at some £20 Chinese wonders with MediaTek MT2502 chips, but I couldn't see how I'd get into them to flash a new ROM and I could't find anyone here using the same model. I've been looking at the MOTOACTV, which I see has many fans, but am also quite happy to consider other (particularly cheaper) alternatives, as long as I'll be able to develop something for them, get to the accelerometer and eventually send data to a server.

Sorry for the long post. Any advice?



Aucun commentaire:

Enregistrer un commentaire