>>BTW, meant to ask - what are you using for the server/db ?
>
>Google App Engine. It's about as simple and powerful and cheap as you could possibly imagine. You literally run your apps on Google's infrastructure for free. (Until usage quotas fill up). So the backend is BigTable, Google's NoSQL database they use for everything including Gmail I think.
>
>To store data you do something like:
>
>

>DatastoreService ds = DatastoreFactory.getDatastoreService();
>Entity recordOfSomeType = new Entity("TheTypeOfRecord");
>recordOfSomeType.setProperty("name", "Mike");
>ds.put(recordOfSomeType);
>

>
>That's it. You don't have to create tables or a schema or anything. Just start writing, and its scalable up to Gmail levels.

Looks good. What sort of capacities do you get for free?
I've been using MongoDB which is similar. Like it because (a) I can easily run a local server/db for testing and (b) it has a pretty good C# driver which I can use if I want. The live server is on Azure and the database is on a Amazon 'W Europe' server.

>>And what devices are you debugging on?
>
>
>I have a few old Androids (given to me out of people's junk drawers), a Nexus 7 (also wasn't be used so it was given to me) and a Note 2 (also given to me).
>
>I usually only use the android emulator to test larger screen sizes or when the app needs to talk to a development server (such as localhost).
>
>I only have an old laptop with Ubuntu on it, so I can test FireFox and Chrome but not Safari or IE as far as browsers go.
>
>As far as Apple products go I just ask my friends if my app works. If it doesn't, I fiddle with it and ask them again.

Emulators don't work well for me ( I need actual GPS information) but I can plug in a Nexus or other Android device to the desktop via USB and debug remotely using Chrome developer tools - either works great or not at all :-}

>iPhone has a Web Audio API quirk where the web page has to receive a click or some user input before it will play sounds, presumably so you're not getting bombarded by sounds from unfriendly web pages.
>
>I was aware of this but not that the actual click event had to create sound for it to be allowed. I was using onclick to fire off a download, and then onreadystate to play the sound. Since the sound was being played by a different thread than the original click handler, it was muted. I figured this out and wrote and published the work around without ever actually touching an iOS device myself.

These things can be painful :-}
I've got a couple of issues with the Google Maps API on IPads that I need to address.....

>
>>I can debug the desktop obviously, IPad using web inspector and most Android devices that I have access to (usually with chrome) using adb but that's about it....