fidanov

Right or not right is subjective as other have said already, so what is right for me, may not be right for you. For me coding right is the following:

1) If I return in a month, I can still quickly understand what the code does. 2) When I modify part of the code I can do it easily without modifying too much other parts of it. 3) Someone else reading my code, who has never seen it before can read and understand it easily.

One other thing to remember is that right code also depends on the project you are doing. What is right for a small quick app is not the same as what is right for a big entreprise application. If there are many people in a project then you may need to code in a more documented way, but the same thing will be overkill if you just test a simple feature.

A great place to learn is from open source projects. Some of them have lots of contributors and if they don't their code right, the project will become a mess. Learn from their practice and apply it.

My very last advice is no matter what you decide is right code, be consistent. Don't code one day in one way and the next day in another way.

Great! There is a need of similar solutions. However, a few comments.

The encryption is interesting but most developers will not care whether it is there or not. So if you don't need it yourself, don't spent too much time on it in future development. That is just an advice.

Second your database creation, is not simple enough.

WaspFactory.createDatabase("/sdcard/","myDatabase")

is simple, but why not having

WaspFactory.createDatabase("myDatabase")

and store the database at some default place (the private folder of the app for example?)

or even

WaspFactory.createDatabase()

and store the database at default place with a default name.

One last thing. Your store seems great to replace the default android preferences, because it can store complex data in a simple way. Keep the good work.