|
I like JBabey's outline the best.
A few things to think about. Apologies if a lot of this has already been mentioned.
-Radio/PRL stuff. Will the app handle this? Or is it assumed that the user will make sure they have latest versions for their carrier?
-Extended ROM. Will the app give any options on this? Full/minimal version by carrier. Extended ROM as an OEM (which I think is the way to go). Extended ROM unlock. Ability to load your own cabs into Extended ROM...etc
-Regarding the above 2 points. Is the app only going to create an nk.nbf or also the radio and extended rom?
-Base ROM options. Need to be careful here. Some things like changing the look and feel or the ability to remove MSN, HTC apps might be no brainers but do we want to give users more options to get even leaner and cut closer to the bone. e.g. removing T9 keypad...etc. and have the potential for more errors.
-Registry edits. Do we just do as Jbabey suggested and let user enter registry changes. Or do we want to provide some built in options for the best the most often used registry changes. Perhaps we sort of build in a version of PPCHacks into the kitchen app. I know a lot of chefs will make their own custom Registry hack OEM that has an .rgu with all their hacks. Perhaps we find a handful of the best or create a handful and let a user just choose one of these as an OEM. Again, lot of room for error here.
-OEMs. Ditto what everyone has said about QCing OEMs. Also, regarding OEMs for commercial software, do we just do as we have been and leave out .exe from the OEM and let the user sort out putting in their own .exe into the OEM before cooking it in... or dropping it in /windows after cooking. This is another argument for downloading OEMs locally so that users can drop in their own .exes, or build in passwords for their purchased software into their .rgus.
Thats all for now. Great work team!
-j
|