Thank you Greg and Jesse for your very insightful responses.<br><br>I'm excited to dip my toes into the iPhone App environment. Mac Mini is ordered and I'm in the middle of reading my first iPhone SDK book.<br><br>
Sounds like iPhone App development has the kind of learning curve that Drupal had... I'll chime back in with my results.<br><br>Josh<br><br><div class="gmail_quote">On Fri, Jun 18, 2010 at 3:31 PM, Jesse Feiler <span dir="ltr"><<a href="mailto:jfeiler@northcountryconsulting.com">jfeiler@northcountryconsulting.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I totally agree with Greg's points except the last one. The iOS learning curve can be very steep (iOS was invented last week to replace the outdated "iPhone OS" name in view of the fact that iOS runs both iPad and iPhone as well as iPod touch--actually it was licensed from Cisco by Apple).<br>
<br>
Build in a big pad and then double it, particularly if working in the physical constraints of an iPhone screen is new to you and it the navigation tools for users on both iPhone and iPad are new to you. Without this leeway, you may get an app up and running but it won't look right--and may not make it through the App Store's review if you trample on the user interface guidelines.<br>
<br>
That said, I'm not certain the client should pay all of this start-up learning curve. First of all, I don't know how you can transfer that expertise to the client after they've paid for it. You'll have that expertise, and as Greg points out, your second iOS app is a lot easier to do. If it's for the same client, that's OK, but if it's for another client, you'll wind up charging the new client much less. Second of all, iOS is a great environment in which to develop once you get up to speed.<br>
<br>
P.S. Read, re-read, and re-re-read the iPhone/iPad user interface guidelines, and think about what it means for users to interact with a computer that they hold in their hand.<br>
<br>
<br>
> Date: Fri, 18 Jun 2010 11:42:18 -0700<br>
> From: "Greg Holsclaw" <<a href="mailto:greg@t2media.com">greg@t2media.com</a>><br>
> Subject: Re: [consulting] iPhone App & Drupal Pricing Ballpark<br>
> To: "'A list for Drupal consultants and Drupal service/hosting<br>
> providers'" <<a href="mailto:consulting@drupal.org">consulting@drupal.org</a>><br>
> Message-ID: <00b901cb0f15$fbaeae10$f30c0a30$@com><br>
> Content-Type: text/plain; charset="us-ascii"<br>
<div><div></div><div class="h5">><br>
> Without knowing the specifics app, it can be a bit hard consider. For our<br>
> Dog Park Finder app,<br>
> <a href="http://itunes.apple.com/us/app/dog-park-finder/id362002678?mt=8" target="_blank">http://itunes.apple.com/us/app/dog-park-finder/id362002678?mt=8</a> , (Drupal<br>
> backend, link for example we don't need more downloads doing fine as it) I<br>
> initially spec'ed it out and got 6 bids. Ranged from $3000 at $20/hr to<br>
> $18,000 at around $75/hr. The low end were all off-shore vendors with less<br>
> provable experience to high end established Houston based group.<br>
><br>
> We decided to do the dev in house (for a myriad of reasons,<br>
> cost/maintenance/desired in-house expertise..).With the learning curve it<br>
> was over 200 hours to develop (but that curve has spun out another app<br>
> already and another to come, all Drupal backend).<br>
><br>
> If you are starting from zero iphone dev experience, you had better add a<br>
> huge pad to your total time estimate. There are many twists both in the<br>
> iPhone and Drupal intregration you will have to account for.<br>
><br>
> If you client is willing to pay for both the product and the learning<br>
> curve, more power to you.<br>
><br>
> Greg<br>
><br>
><br>
> From: <a href="mailto:consulting-bounces@drupal.org">consulting-bounces@drupal.org</a> [mailto:<a href="mailto:consulting-bounces@drupal.org">consulting-bounces@drupal.org</a>]<br>
> On Behalf Of Josh<br>
> Sent: Friday, June 18, 2010 11:08 AM<br>
> To: <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
> Subject: [consulting] iPhone App & Drupal Pricing Ballpark<br>
><br>
> Hello Fellow Drupalers!<br>
><br>
> I'm starting iphone app development and have plans to make a Drupal-powered<br>
> back-end for some of the more mundane parts of the new iphone app (News,<br>
> Directory, Locations, etc).<br>
><br>
> Does anyone on this list have experience with marrying those two<br>
> technologies? Most of our websites start at 75 hours and go up from there<br>
> into the 600 hours range. (Think $7,500+ for our clients.)<br>
><br>
> When I estimate our time for an iPhone app, we're getting close to 130<br>
> hours+<br>
><br>
> Does this sound right? Do you think your clients would pay for iphone apps<br>
> in the $13,000+ range? To be honest, this feels high. But with very little<br>
> experience in the iPhone app world, this may be low.<br>
><br>
> My apologies if this message somehow violates the protocol for asking these<br>
> kinds of prices. I'm not looking for someone to do the work, I'm just<br>
> looking for some feedback who do this work as well.<br>
><br>
> Josh<br>
><br>
><br>
> Josh Miller WEB / TECHNOLOGY DIRECTOR<br>
> HAAN MARKETING+COMMUNICATIONS<br>
> T (765) 423-5470 123 North 8th Street<br>
> F (765) 742-2881 Lafayette, IN 47901<br>
> <a href="http://www.haanmc.com" target="_blank">www.haanmc.com</a><br>
</div></div>> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <a href="http://lists.drupal.org/pipermail/consulting/attachments/20100618/094427a8/attachment.html" target="_blank">http://lists.drupal.org/pipermail/consulting/attachments/20100618/094427a8/attachment.html</a><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> consulting mailing list<br>
> <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
> <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
><br>
><br>
> End of consulting Digest, Vol 53, Issue 15<br>
> ******************************************<br>
<br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</blockquote></div><br>