Linked by Thom Holwerda on Thu 13th Sep 2012 21:44 UTC
Thread beginning with comment 535070
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2009-07-08
Very cool, but your data access layer would have to be self-written/managed on both platforms. It's obviously not going to translate the Android content provider API, and I don't see how it could work with iOS' CoreData, so you'd have to manually do your DB data reading/writing code, right? That sounds like you'd end up with a horrible Frankenstein app, but I don't know. If Google is using it on some of its iOS apps (would love to know which), there must be a way to do that better.
For projects without huge resources, it sounds great. But ideally you'd write each app from scratch. I have no idea why Google would be using this itself.
And for all the people talking about MonoTouch: hahahahahaha.
Edited 2012-09-14 15:58 UTC