Droid?

[Krensky]

what's it matter?

If someone writes a super cool DND app for the Droid, it'll still work on the Droid eris, and the G1, and the Mytouch3g, and the samsung moment, and the Acer A1, and the Galaxy, and the Hero, and...

So why are we fighting over which phone is a "droid"

Well, to be precise apps written for the Motorola Droid might not run on other Android phones, particularly if it uses services or features in Android 2.0 not found in earlier versions. Similarly, apps written with other devices in mind might not be usable on the Moto Droid depending on their interface. The Droid's screen is so much larger and has a much higher resolution, so interfaces that work on an G1's screen, might be unusable on the Motorola Droid because the text and buttons are too small.

There might also be problems depending on what the app does and what sensors and what not it uses. A compass app won't work if the phone doesn't have a magnetometer, for instance.

As for why we're quibbling over it (nothing here approaches 'fight'), we're geeks, it's what we do.

 

[Scribble]

I haven't found much beyond dice rollers myself, though the "Scryer" website (Scryer - D&D Insider Compendium Searcher) is nice for a front-end into the DDI Compendium. There's also a power card site (DnD 4e Power Cards Index), though I haven't looked too closely at that one.

I've recently started to delve into Android development, so hopefully before long I can put a few apps out there. In particular, I'd like to port TableSmith over to Android.

Thanks for the links! Those seem pretty useful.

 

[Moon_Goddess]

Well, to be precise apps written for the Motorola Droid might not run on other Android phones, particularly if it uses services or features in Android 2.0 not found in earlier versions. Similarly, apps written with other devices in mind might not be usable on the Moto Droid depending on their interface. The Droid's screen is so much larger and has a much higher resolution, so interfaces that work on an G1's screen, might be unusable on the Motorola Droid because the text and buttons are too small.

There might also be problems depending on what the app does and what sensors and what not it uses. A compass app won't work if the phone doesn't have a magnetometer, for instance.

As for why we're quibbling over it (nothing here approaches 'fight'), we're geeks, it's what we do.

Well, 2.0 actually 2.1 is going to be offered as an update for all previous phones except the Dream (T-mobile G1) and Cyanogen has got most of 2.0 already running on it, should get all of it as soon as we get the drivers ripped out of the magic.

The SDK actually calls for UI resizing, it's been long known ever since 1.1 that we were going to have different resolutions on different phones. App developer might not all support it but at least 90% of them do. Likewise the market has systems in place to no show you apps that have say a compass feature if your phone doesn't have one (is there one? I havn't seen one without)