Now i have already discussed on Why you should Build a Rom and make it Public, and if you are here then either you must have been through the other 2 parts of this Article or you should go through them before reading this. This article makes you aware of the tips and techniques that you need to keep in mind while being a Rom Developer for Windows Mobile Phone Device. This is the 2nd Part of the 3 Part series of this article.
Keep Detailed Changelogs
Changelogs keep track of your developments over the time. They come in handy when ever you need to check for prolonged bugs. For example you may not notice it but if someone reports that he has been having an issue since your 3rd Rom release, then you can check out what all changes you made on that release and cross check whether one of those changes cause that bug. It helped me always.
Provide Regular Bug Fixes
In every release there might occur a small bug which can easily be fixed by making a small change to the Rom and remove the Bug. This can provided in terms of Cabs or a small Note on how to fix it. In order to know how to build cabs read my post on How to make Cab Files.
Trial and error
Nothing will succeed unless you apply hard work. And many times a bug solving requires alot of trials and tests. I still remember i hade to flash my device 36 times before i could solve my Active Sync not working. In the end i ended up with one packages and that too in which one wrong registry entry was causing all that issue.
Give Consistent Release Time: Not too Often and Not too Late
Let the users use your Rom for sometime before you hand over another release. They might like your Rom but flashing every other day is a pain in the A** cause of the time it takes and then backing up the data. Until its a major Bug fix or a Major development which cannot be fixed by just a simple fix cab. Give time for people to use your Rom, test it, report their experiences and then proceed towards the next release.
Be Active on the Rom Page
This is the most important part of being interactive with the users cause there is alot that they want to be done in your Rom. Talk to them, answer their questions and discuss the pros and cons of the Roms with them. You can learn alot from them. Being active to the discussion will make them feel that you are eager to further develop and make this Rom improve further.
Add only Useful apps and Regularly Update them
Make sure the application you add to your Rom are useful by the people. Adding two IM Messengers in the Rom is not a good choice. Choose one that is best and use that only. But make sure you add one possibly best application for all needs of the users. You can read our article on Best IM Messengers on Mobile Phone. Keep track of all the applications that you have included in your Rom and make sure the latest versions are included. It keep the user feel updated with your Rom. Many times there are applications which are important to add but have some bug. Later these bugs are fixed in their next releases, so even you should add those updated fixed applications.
Use only Genuine Licenses and No Warez Applications
Warez is like a virus to the development of your Rom. Copyright issues and illegal use of cracked applications make pose a ban on you Roms by the Blogs and threads where you list them. Either you use development licenses to use the in your Roms or use an equally good free Application.
Make sure a Backup Application is included
Backup applications are very important to be present in every Rom as after a user formats his device the 1st thing they do is Backup their previous Data. So it is important to include a Backup Application that is widely used. You can check out my post on Best Backup Applications for Mobile Phones.
Release different versions for Users
Many times we jus release the version that we personally use. Now that might appeal to only a few people who have needs similar to you. But what about those who like your Rom but wanted more additions, what about some who wanted things to be less. Well that is where customization is required on different versions of your release. For example- Full, Lite, Clean based on the quantity of applications included.
You can read the rest of the parts Below:
You can discuss your views Below.
