Chess Tiger for Ipad/iphone etc.
Posted: Tue Mar 08, 2011 9:11 am
Independent Computer Chess Discussion Forum
https://open-chess.org/
I like the graphics and the GUI.thorstenczub wrote:http://itunes.apple.com/us/app/chesstiger/id423198259
Christope Theron from TalkChess had this to say about AndroidSwaminathan wrote:I like the graphics and the GUI.thorstenczub wrote:http://itunes.apple.com/us/app/chesstiger/id423198259
I wish there was a version for Android.
I think Chistophe's real reason for abandoning Android is that it's easy to decompile Android programs back into Java source codeCubeman wrote: Christope Theron from TalkChess had this to say about Android
Posted: Wed Mar 09, 2011 10:40 am Post subject: Re: Daily iPhone chess programs releases
The answer for both question is that I do not know.
Android: while it may look like a fine platform from the user point of view because the phones/tablets are not expensive, look like they have most of the features of iOS devices and there is more choice, I'm not convinced by the platform as a developper.
In Q1 2009 I had decided to write an Android version of Chess Tiger. I had correctly predicted that Android would take a significant smartphone market share. But after carefully reviewing the platform and the ecosystem around it I decided to change my mind and to go for iOS (then known as iPhone OS) instead. I wasted 4 or 5 months by changing my mind, but I think I took the right decision.
Now, 2 years after, my analysis of Android has not changed. I find it technically inferior (I was surprised by the quality of Apple's software, which I did not know at all before October 2009), Google does not care about the developpers, and it's a platform designed to produce cheap smartphones for people who will almost exclusively want free applications. And all of these phones are and will always be subtly incompatible with each other.
It's natural that it is a big success.
Again, you as a user can find that the Android devices are great, not as expensive as Apple's devices and functionnally equivalent. So they naturally may look more attractive.
I can understand that.
// Christophe
For the GUI, perhaps it would be easy. But the engine would be compiled as a native executable (Google NDK), not Java bytecode. It would be no easier or harder to disassemble than existing versions.Ron Murawski wrote:I think Chistophe's real reason for abandoning Android is that it's easy to decompile Android programs back into Java source code
http://stackoverflow.com/questions/1249 ... sourcecode
I have never worked on mobile apps, so I didn't know about Google's NDK. Thanks for the info!UncombedCoconut wrote:For the GUI, perhaps it would be easy. But the engine would be compiled as a native executable (Google NDK), not Java bytecode. It would be no easier or harder to disassemble than existing versions.Ron Murawski wrote:I think Chistophe's real reason for abandoning Android is that it's easy to decompile Android programs back into Java source code
http://stackoverflow.com/questions/1249 ... sourcecode