Thursday 11 August 2011

Eclipse build workspace task stuck

Today I have strange problem with Eclipse. When I try to configure build path of one of my project Eclipse start to build workspace but couldn't finish. Build workspace task just hang.

I have to start task manager (TIP : in Windows you can do that by pressing CTRL+SHIFT+ESC keys)and kill Eclipse process.

I ask Google and find this page http://www.eclipsezone.com/eclipse/forums/t61566.html. There was advice there to run Eclipse with -clean parameter. And it work like a charm :).
But what this parameter do? From Eclipse documentation :
if set to "true", any cached data used by the OSGi framework and eclipse runtime will be wiped clean. This will clean the caches used to store bundle dependency resolution and eclipse extension registry data. Using this option will force eclipse to reinitialize these caches.

Lot of more information you can find on article mentioned above.

Wednesday 10 August 2011

5 Android developers mistakes

There is a lot of mistakes you can make when you develope new application. I want to show you 5 of them I found to be important.

1.Soon release
Developers often think that they should release their application as soon as possible. It is true but you have to remember that your product should be complete before you can sell it. Image that you just bought a bread but it is baked only in half ;). Remember to always implements core functions before you release application. Some people may argue and say that when you release you have feedback from your users. It is true but remember that in Android Market each user can give a rate to your application. If it lack of main functionality people will rate it low. It is always better to take your time and make you application a “killer app”.

2.Lot of bugs
This problem usually comes with soon release. When you want to release soon you software is not well tested and usually full of annoying bugs. Always make at least this tests :
*Check your application in as many resolutions and screen destinity as you can. You can do that by creating custom Android emulators using SDK.
*Simulate usually use of phone. Try to response to income call when your application is running, answer to incoming text message etc.
*
It is impossible to find all the bugs in your application (every not trivial software have at least one bug).

3. Commercials only apps
Developers often create application only to put commercials in it. They put commercials in each screen of they app. Remember that people doesn’t like this boxes. They can click it to appreciate your work or because commercial is interesting for them, but if you design your application in way that users can click in commercial by mistake sooner or later (often sooner) people become irritated by your program and they will uninstall it. Android Market gives you tools to monitor how many active installations you have. Even if your goal is to make money on commercials remember that your application have to be useful first.

4.Too often updates
When you release your application you will get user feedback or bugs reports (Android Market give you great tool for bugs reporting). Don’t try to implements new features or fix bugs as fast as possible and release new version. I suggest to plan update once a week or even one update in two weeks periods.This have another advantage : you application will be shown in “Just in” applications in Android Market. Make a lot of small updates may irritate your users.

5. Ignoring users requests
User pleasant should be always main purpose of creating a application. If you will listen to your users and make changes as they request your application will be popular and will bring you profits. People often leave comments in Android Market and let you know what is wrong with application or what should you add. It is grate source of new ideas and improvements.