4 ms·

Three weeks is pitifully small when coming online with android. The tools are much much less good than iPhone. You're not really programming java per se, as a

by gte910h 17y ago

Three weeks is pitifully small when coming online with android. The tools are much much less good than iPhone. You're not really programming java per se, as a java like language missing half the API's you're used to. If you PM me a link to the iPhone app, I'll tell you my guess at a timeframe. Secondly, the G1 (which runs 1.6) is not the lowest common denominator at the time. While it does have some of the wimpiest specs, other phones, such as the Moto Cliq, are still stuck on 1.5. Additionally, I suggest you check out http://commonsware.com/Android/ http://commonsware.com/Android/ which had a nice section on scripting on the phone, which was invaluable for testing out UI design alternatives. Not seeing your iPhone app, I honestly suggest telling them "This could take between 2 and 10 weeks, and will likely take more like 5 or 6". While you're probably keen on eclipse, also check out how to develop without it, so you can use the debugger without eclipse getting in the way. It is a tad bit unreliable at times.

wallflower 17y ago
I'm revising my estimates based on the feedback you and others here have provided, and I'm still going to dive in. The app is a fairly typical CoreData-based tab bar app that makes heavy use of Google Maps (MKMapView) and UITableView. There is some custom UI in it but it's not that critical to the overall app. To minimize risk in my approach, I'll address learning how Android's UI architecture works by just trying to create an app and tie screens together. And have a parallel lower-priority going on how to get some semblance of ORM (reading , not updating data) on the G1.
- gte910h 17y ago
  As far as the data goes, I believe you'll be able to get something going relatively easily that is a good enough replacement. If you can ditch the custom UI for the app, that will help, as again, that's much harder in the Android world than the iPhone world to start with. If all else fails, for a V1 (if this is only readonly), you can always write a program to dump your database into a java class which "hardcodes" the data. Remember, you can update to the store in seconds on android. No review process, takes only 20 minutes or so to sign up for the whole developer account. Additionally, this Really got me when I started with it: You can't see the paid apps on the android store if you don't link your phone to a google account with a valid google checkout profile. I made a fake google account on the dev phone (which I wasn't sure I was keeping), and was confused as hell during the upload process because of this.

by gte910h 17y ago

wallflower 17y ago

I'm revising my estimates based on the feedback you and others here have provided, and I'm still going to dive in. The app is a fairly typical CoreData-based tab bar app that makes heavy use of Google Maps (MKMapView) and UITableView. There is some custom UI in it but it's not that critical to the overall app. To minimize risk in my approach, I'll address learning how Android's UI architecture works by just trying to create an app and tie screens together. And have a parallel lower-priority going on how to get some semblance of ORM (reading , not updating data) on the G1.

gte910h 17y ago
As far as the data goes, I believe you'll be able to get something going relatively easily that is a good enough replacement. If you can ditch the custom UI for the app, that will help, as again, that's much harder in the Android world than the iPhone world to start with. If all else fails, for a V1 (if this is only readonly), you can always write a program to dump your database into a java class which "hardcodes" the data. Remember, you can update to the store in seconds on android. No review process, takes only 20 minutes or so to sign up for the whole developer account. Additionally, this Really got me when I started with it: You can't see the paid apps on the android store if you don't link your phone to a google account with a valid google checkout profile. I made a fake google account on the dev phone (which I wasn't sure I was keeping), and was confused as hell during the upload process because of this.