I don't have actual experience doing this in Android, but I can offer some suggestions from general experience with Java and software archtecture.
How much can you exploit MVC? What part of the code is the View? How much of the code is the Model? If a large part of the code is the Model, that is the business rules, logic, data conversion, etc., then there's a good chance that with some refactoring, you can get that part of the code to run on Android after some refactoring. Unless the code was actually architected to run on different platforms - which it probably wasn't, blinded by the sirens of WORA - chances are there'll be some painful refactoring. BTW, is the existing code base covered with unit tests? That would help. My rule of portable code is: "Code isn't portable until it's been ported." -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
