Thursday, July 29, 2010

Light Meter 1.0 released on Android Market

The release of 1.0 EAP has been getting great responses. In less than 10 days, it got 866 downloads and 11 ratings with an average of 4.5 stars. So here is the 1.0 release.
Changes
+ calibration so that it can work with different ambient sensors on different phones.
+ be able to remember settings
Two help related features pushed to 1.01
Enjoy.

Sunday, July 25, 2010

One Polish comment on LightMeter 1.0 EAP

It says "Aplikacja która w przyszłości może będzie dobra, ale na razie jeszcze dużo jej brakuje."
Google translate told me that it's Polish and in English it means "Application that the future can be good, but for now its still a lot missing."
I guess this user must haven't seen the statement I put in the market: "This is an Early Access Preview version , so very premature yet."

The commenter left a rating of 2 stars which changed the 100% 5-star rating so far (5 ratings before this one)

Lesson learned: you can never go too far to manage user expectations.

Monday, July 19, 2010

Road map for Light Meter

1.0 - add calibration function so that the app can work with ambient sensors from multiple manufactures.
1.1 - add depth of field calculation
1.2 - add hyperfocal distance calculation
1.3 - add a depth of field priority mode.

Light Meter 1.0 EAP released.

Go to your Android Market and search for "Light Meter."
It's an Early Access Preview version with only very basic functions.
Give it a try and send me feedback if you would. I will really appreciate it.
Thanks!

Saturday, July 03, 2010

Android UI Test note

If you are using the ant script to run the ui tests, that script only detects changes in the java code in the target and test project. The R resource file is somehow not included. If you make any change to the layout which requires some change in the R file (your IDE might be able to help you with that), if you then immediately run a simple "ant run-tests", you might get some weird error. It seems that the new layout file has taken effect while the R file has not. In this case, you need to run a "ant clean compile" in your target project and then "ant clean run-tests" in your ui test project.