Thanks for sharing. I've looked briefly at your code and I'm a bit worried about how un-android like it is. For example:
- Prompting the user when the app is "exiting": normally a user familiar with Android app will know that the back button will take them back to the previous activity - Killing your process onDestroy...why? - Managing views in one activity: I understand the code over configuration thought, but I don't think this will cover all cases that would be covered if a screen would be a separate activity. What about restoring state when your app was in the background and it got killed by the OS? Why manage the view navigation at all if you can let the OS do it for you? You seem to be managing other stuff that Android will already manage for you, and I'm not sure if it's worth the trouble and the potential bugs. I hope this doesn't sound too harsh or anything, I just wanted to let you and potential users of your framework the concerns I mentioned. Hugo On Apr 25, 2:28 am, Brian Knorr <btkn...@gmail.com> wrote: > Hello all, > > We developed the popular mobile travel application TripCase > (http://www.tripcase.com) natively for the iphone, backberry, winmo, and > recently Android. We really like the Android framework compared to > the others, but found some of it's concepts like Activities to be very > cumbersome when dealing with screen based applications like ours. We > have many forms and workflows, lots of viewable and editable data, and > we make many calls to our back-end Rails server. In order to > streamline our development efforts on Android we created a small > convention-based micro-framework which we are calling DynaDroid and > would like to open it up to the Android community for use. > > http://code.google.com/p/dynadroid/ > > Here are some of the features that you get with DynaDroid: > > * The entire micro-framework is housed within a singe Activity, so > sharing data between screens is finally easy again. > * Code by convention and all your xml layouts and menus are > dynamically available. > * Screen management for pushing, popping, and swapping screens > (all with transition animations). > * Screen orientation (landscape, portrait) can be controlled on a > screen by screen basis. > * Error reporting support built-in, so if your app crashes a > report is sent to you. > > And there is more to come: > > * More dynamic coding conventions - let's get rid of all those if/ > else and case statements! > * Built-in screen analytics for tracking user interaction > * Simplified device to server communication with xml/json parsing > and automatic error handling > * Extensions to Android UI components without all the plumbing > * Easier to use api for interacting with device capabilities > (camera, gps, phone, etc..) > > We would love your feedback on the micro-framework...so please let us > know what you would like in the future. And if you have any questions > or issues our Google group is located here: > > http://groups.google.com/group/dynadroid > > Remember DynaDroid is already being used in the production Android > application TripCase, so it's been thoroughly tested and is ready for > prime-time. > > Enjoy! > > Brian Knorrhttp://www.starterstep.com > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group > athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
