I have run a version of the iPhone since they first came out.  The only thing stopping me right now from picking up  an Android phone when they are available from AT&T is the state of their app store.  It's where the iPhone app store was about 2-3 years ago.  

I am definitely picking up a Android table, perhaps the OLPC one when it is available, simply to develop against.  As little as I know about iPhone development I think C# is a language it supports even though it has to be a special version.  In my discussions with a friend about Android development, we agree that if the business logic was developed in a class library with Mono (an open source C#) it could be deployed against iPhone(maybe), Android, and XNA given that you would still need to redo the user interface.  Rewriting a UI still would take considerable time.

I would love to see other versions of 100 rogues, but I understand the complexity of what it would take to make it happen. 

Keith Burgun said:

Right now, however, our priority is on REALLY fleshing out the iPhone version, and making sure that everyone who bought it and buys it feels like, "hell yeah, this was SUCH a great purchase".

it's kind of a golum act to possess this game… "my precioooous" :)

Fraggle Rogue said:

Keith Burgun said:

Right now, however, our priority is on REALLY fleshing out the iPhone version, and making sure that everyone who bought it and buys it feels like, "hell yeah, this was SUCH a great purchase".

---

In my opinion, everybody's here and anyone who purchase 100 rogues already think this.
 

it's kind of a golum act to possess this game… "my precioooous" :)

QFT

100 Rogues = my biggest iPod timesuck. Even over Phoenix Wright, Carcasonne, solitaire, and other neat games I have (and I have quite a few).

You really should release an Android version. There's Dweller, which is a rogue-like, but 100Rogues looks like it's a lot better!

I don't want an Android port, I just want an updated iPhone version: when you finish it, do a great sequel (200rogues? :P)

I've started to dig around in the AndEngine and it's looking like it will be suitable. Writing the engine from scratch is something I could do but without the smooth animations I'm sure everyone will want.

@samgreen: Unfortunately after speaking with Wes about the port in a little more detail it's looking like a pipe dream. The problem isn't so much the creation of the port itself but the time and effort it will take to maintain a port that is written entirely in Java and is completely separate from the existing Objective C engine (using cocos2d). Not to mention Wes's estimation (and likely an accurate one) is around a full year of work (maybe more like 4-6 months if we were to collaborate) before we would have something ready for the Android Marketplace. In Wes's opinion (and again, I agree here) that sort of work is simply not worth it for an Android port (in the unproven Android Marketplace). With those thoughts the port has turned into more of a learning experience for me rather than something that will actually be brought to market. If we were to work on a port we would also want to work on a platform that would allow the games to be developed in sync leveraging the same code… something like this just isn't possible as of now without a full rewrite of the game engine.

Wes, you've confirmed my understanding of the situation – perhaps I wasn't clear in my post. Thanks!