Too Many Updates?!

-
While browsing through some recent comments posted on the Android market, I was surprised to read that some users complain that I am pushing too many updates. I usually work on these games in spurts, i.e. a lot of improvements in a short time followed by a period of relative quiet. Another problem is that the Android market does not enable me to push updates to specific platforms or builds only. So, for example, when I fix a bug for Android 1.1, some users will not see a change, but others may be happy to receive an update. Last, the Android market does not support a good way to show revision history.

Luckily not all users feel that way, as reflected in the comment:

Updates are a pain? Really? its wonderful when developers continually work on their FREE app to improve it. Be thankful not frustrated.
Vin Fri, Feb 12 11:47:00 PST 2010

Thanks Vin!

Comments

zavoor.blogspot.com said…
Its an interesting matter with truth somewhere in the middel :-) i was started slightly to get the same feeling.
The centre is a communication problem: hpw do i visualise to the public the update-"pattern"?
It seems logically wise to do it graphically.
Like a monitor shows processor-activity.

I have more of a problem with the attitude as if anyone is okay for announcing updates. Its nice to "agree" developers all for 100% trustworthy but not realistic. It requires enough 'identification'
I suppose the bit-population too be too much used to be the bit-cattle of MS, and i really got
a very kind of allergy by the Redmond "upditis"...
(Mainly for lacking openness)

Its a beautiful game likely to donate for.
February 12, 2010 at 1:43 PM
Pim said…
Fully agree - with both arguments.

As a user, Android's lack of a batchupdate-button annoys me (I'm on 1.6). I spent most of my commuting mornings updating my apps... There is something very (strangely) disturbing about having apps that are NOT UP TO DATE (imagine!).

On the other hand, I haven't chosen an open platform for no reason - that's part of the package. There is indeed something strangely satisfying about having your apps supplied by people who actually care ;-)

Google should give devs the opportunity to push to version X.Y (and users the choice of batchupdating).
March 14, 2010 at 2:31 PM
Post a Comment

Popular posts from this blog

Checkers Move Generation

-
I was able to make a small improvement in the checkers move generator (written in Java for the Android SDK). The following table shows run times of several perft depths before and after optimization when run on the emulator (which should mimic actual run times on the phone quite well). DEPTH #LEAF NODES ORIGINAL OPTIMIZED TIME TIME ==================================== 7 179740 2.9s 1.9s 8 845931 14.2s 9.7s 9 3963680 66.3s 45.6s 10 18391564 294.6s 208.7s P.S. Runtimes for a C++ checkers move generator on a 2.2 GHz Core 2 Duo are given at my checkers page .
Read more

Connecting Chess for Android to a Remote Server

-
Image
I have received several questions on how to connect Chess for Android running on an Android device (e.g. a phone) as client to a remote chess server (e.g. a powerful desktop), so I decided to write a small document with detailed instructions. What you will need: The server software from Bernhard Wallner's chess utilities , suited for your server's operating system (if, say, your desktop runs Windows, you will need to download the Windows version). You do not need to download the client software in this case. The network enabled version of Chess for Android . On the server, start the engine server software, and construct a new row for every engine you want to run remotely. Assign a name, port number, and select the full path to each engine binary (an executable that runs on the server). You can also supply command line options for starting the engine. Check the active checkboxes and click start when done. This yields something similar to the screenshots below. Here, I have s...
Read more

Connecting with the DGT Board

-
Image
After all the fun I had connecting Chess for Android with the Millennium  over Bluetooth, I was curious if I could provide similar support for the DGT electronic chess boards. Some of these have Bluetooth capabilities, most use USB connections, and some older models, like the one I have, still use the RS-232 connector. To my pleasant surprise, by combining the original serial cable of DGT with a USB-to-serial cable and a female-USB-to-USB-C cable, I was able to get an actually working connection between my DGT board and my tablet or phone. Next was implementing support in Chess for Android. Luckily, DGT kindly shared the protocol documentation with me, and after a fun weekend of hacking, Chess for Android now proudly supports DGT electronic chess boards as well.
Read more