If a lot of your activities display data in tables or such it would be wise to use something like MonoTouch.Dialog to create these parts. Though if you have a lot of custom views where you manually draw stuff it will be a bit more work.
I did some custom controls displaying some graphs where the logic was almost 100% reusable while I just called the MonoTouch equivalent methods to draw things, which worked almost flawlessly. Timewise it is hard to exactly tell you how long it is going to take, but depending on the complexity it would take about 5-10 workhours per activity, a lot less for the less complex ones. What will take some time would be to get used to how iPhone works. On Tue, Sep 4, 2012 at 3:12 PM, Jonathan Chapman <[email protected]> wrote: > We've created a very large line of business application (100+ Activities) in > MonoDroid and are looking to move it to Mono Touch. The structure is such > that the business logic are in separate libraries so we are anticipating the > majority of changes to be in the screen architecture. I was hoping someone > could give guidance on how long it took them to move an application from one > to the other. Note: We currently have not done any iOS development. > > Regards, > Jonathan > > > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/MonoDroid-to-Mono-Touch-tp5711679.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid -- Med Venlig Hilsen / With Best Regards Tomasz Cielecki http://ostebaronen.dk _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
