Big or small. Fast or slow.

I have enjoyed working on AMM and sharing it with everyone. But some changes take longer to implement than others and would take longer to release. I am however also weary about keeping the application fresh and showing that progress eis being made even if they are just small ones.

This doesn’t mean that I will be putting out daily builds.  But I’m going to try to have up to two updates a week.  That way I can roll out small improvements as I develop them and hopefully in between those I will also be able to put out some major changes as well.

So now that I’ve set some targets lets see if I can stick to them :)

Thank you

One thing I forgot to mention in my last post was that for this release there a few nice internet samaritons that help me test AMM.

So I want to thank them for helping me and taking some of the workload. I really appreciate it.

I am now considering running a public beta so more people can get involved. So watch this space.

AMM 1.2 Released!

AMM 1.2 is now out in the Market.  I’m very excited about this release because it is the start of some of the new features to come.  To see what has changed you can check out the change log so I won’t repeat them here.  But one of the changes I would like to mention is the anonymous data collection feature.

This feature is currently turned off by default but I really hope people will turn it on as this provides me with a lot of useful information to understand how the app is being used.  I would also like to hear your opinions on whether I should turn it on by default.  I know this app only has a small user base but I also know that collecting data can be a contentious issue.  But I personally would like to keep it on as the data is anonymous, doesn’t harm the user (except possibly if you have to pay for the data charges) and provides me with a lot of value.

Anyway, it’s getting late so I’m going to leave it at that.  As usual, download, enjoy and spread the word.

A bitter sweet weekend.

First the good news.  This weekend I managed to recruit some beta testers (thanks guys.) and now I can see some numbers on Fluffy Analystics and get some demographics of my users.  And I have to say from what little data that has been collected I’m surprised at the data.  I hope to share some of the information collected with you guys once there is a better sample.  Don’t worry.  I can’t see where you are or what you doing.  Twitter and Facebook probably can tell me more :)  All I can see is which continent you are and what type of phone you are using a few more things about how you use AMM.  And as mentioned all the data is completely anonymous.

With the beta also came the option for users to email me an exception log if AMM force closes.  This will be a big help for me to debug an issues people are having.   So generally I am quite excited about the next release which should be in a day or two.  I am also going working on other things to extend the application.

The bad news?  For the first time the number of active installs for AMM has dropped.  I was a bit disappointed by this as I have been working to improve the retention rate of AMM.  It seems the main problem is people don’t know what it does or they don’t see improvements, maybe even both.  So I’m working on a help file and the FAQ.  I would like to change the 6 app categories but it’s a bit tricky as the basis of what AMM is doing is technical.  I also don’t want to run the risk of misinterpreting the categories.  One thing I am going to do as of the next release is to change the default setting to Mild so that people should see immediate improvements the moment they start using AMM.  Hopefully this will show users that AMM can actually improve the user experience of their Android phones.

So, hope everyone had a great weekend and look out for an update very soon.  :)

German or Dutch?

I’ve just processed all the text in AMM through Google Translate and so now users can see all the text in either simplified chinese, tranditional chinese or spanish.  Since I don’t speak any spanish I had to fully rely on Google’s translation.  I’m sure it’s no where near perfect so hopefully some of my users will be able provide me with more accurate translations.  My chinese isn’t great either and I can’t type chinese on my computer so was limited somewhat to what I could do.  But anyway, I hope this makes the app slightly easier to use for those whose first language is not English.

In the middle of doing this I went to Androlib.com to do my daily check of the stats for AMM.  To my surprise today is the first time that it shows that I have German users.  So Hallo to you!  I tried translating the app to German but Google couldn’t translate most of the words so I decided to just leave it for now unless some one can provide me with the translations.

Anyway, look forward to hearing feedback/complaints.

AMM aka 自動內存管理 aka administrador de memoria automática

Now that AMM 1.1 is out of the way and save-on-reboot issue is out of the way I can start working on localization of the app.

And at this I am impressed. It is quite easy to localize the app. I do need to reorganize some of my fixed text into the string.xml file but that is quite straight forward.

I’ll be using Google Translate to do the translation so it’s not going to be the greatest so it would be nice to give me feedback on the translation. I will be doing localization for traditional and simplified Chinese and Spanish as these look too be the main people downloading the app. I will add more languages if they become popular.

Good service provided.

After a week of experimenting I’ve finally implemented the “on boot” functionality for AMM. So now your settings for AMM will still be kept and applied after a reboot.

Unfortunately due to some wifi issues at home I will only be able to upload the update a bit later. But it should be a good one.

AMM 1.0.4 released.

As mentioned in my previous post I’ve changed the workflow of the app. Hopefully for the better.

This is how it works now:
* To use one of the presets just press the button. The sliders will update to show what the settings will be. You can switch around and have a look at the other settings as well. When you are happy with the settings then just press the Apply button to apply the settings. A message will be displayed when this has been done.

* At any stage you can change the options manually in the sliders and press Apply to use it.

* Another less obvious change is that your settings are now saved after reboot. Unfortunately you will still need to start the app up at once before it will automatically apply the settings. I am working this step so hopefully it will be done soon.

So go forth and update.

Sometimes change happens too fast.

When I started making Auto Memory Manager (AMM…I really need to come up with a better name for this app) one of the things I tried to do was to let the user configure and apply the settings in as few steps as possible.  With this in mind I made it so that settings would get applied when a user pressed one of the buttons.  After looking at the feedback from Market and other friends it seems that this isn’t as intuitive as I imagined and has cause some confusion.  So the next point release as well as tidying up the code I’m going to also change how the buttons work so that it will be more in line with what people expect to see.

At this stage I will use the traditional select and apply model which is the most obvious (I hope).  The preset buttons will show the users the settings on the bars and when they have chosen the settings they want to apply they can press the (new) Apply button.  For a custom setting users can just play around with the sliders and press the Apply button.  Sounds simple/obvious enough?  I hope so.  :)

The Secondary Progress

image

A little known feature (I think) is the secondary progress. This a shaded progress on each of the sliders.

What it does is show your current settings. This is useful to as a reminder of what settings you are coming from especially when setting up a custom configuration.  The only problem is that the main slider is not transparent so you can only see the secondary progress if the main slider is less than the secondary slider.

Some may find this useful, some may not. At any rate give it a go.