Welcome to our blog

Jan 05 2010 ∞

How To Hire an iPhone Developer - Tips from the Trenches

Tips and tricks to make your iPhone project a success, based on interviews with over 25 published iPhone developers.

Table of Contents


Background

Apple’s iPhone has become the mobile computing platform of choice for both consumers and businesses. with tens of millions of iPhones and iPod Touch handhelds now in circulation, over 100,000 apps in the Apple App Store and billions of apps downloaded to date.

Tech-savvy business owners and entrepreneurs are taking advantage of this new platform to reach their customers in new ways, becoming an ever-present resource in their customers’ increasingly mobile lives. The iPhone platform allows application publishers to deliver information, offers and personalized service to their customers no matter where they are, and in some cases to customize these services based on time and location, increasing the relevance and perceived value of their offerings.

iPhone design and development is such a new technology skillset that most business organizations don’t have in-house teams capable of creating customer-delighting iPhone applications. As demand for iPhone development services has grown, many developers have expanded their offerings to include iPhone app production, but not all of these firms have a track record in successful iPhone app development and publishing.

The study that follows should serve as a useful guide to any firm or entrepreneur seeking to have an iPhone app developed by a third-party developer.



About AppStoreHQ

AppStoreHQ is the leading independent search engine for iPhone apps. In addition to our search and discovery offerings for iPhone applications, AppStoreHQ offers a range of services to make it easier to find, evaluate and contract with published iPhone developers. These include:
  • iPhone Developer Directory - the only comprehensive, searchable directory of published iPhone developers on the web. The directory allows businesses to screen for developers with specific skills, a track record of success, and the willingness to develop apps for hire.

  • iPhone Developer Forum - AppStoreHQ is the operator and moderator of iPhoneDevSDK, the leading independent community for iPhone developers, with more than 20,000 registered members. iPhoneDevSDK is where developers connect to help each other succeed - both as developers and as businesspeople.
As an active participant in the iPhone application ecosystem, AppStoreHQ sponsored this survey as a public service to iPhone developers and their current and future clients. Our goal in publishing the survey is to increase the chances that iPhone development projects produce successful results for clients and developers alike.



Problem Definition: Hiring and Working with iPhone Developers

Any custom iPhone app development project runs the risk of failure, for reasons including poor project definition at the front end, weak marketing and promotional support post-launch, and dozens more potential pitfalls in between. Broadly speaking these risk areas can be broken down into the following core areas:
  • Understanding the iPhone App Marketplace
  • Knowing What You Want to Build
  • Selecting a Partner Who Can Build It
  • Creating Realistic Project Budgets and Timelines
  • Understanding and Supporting The Development Process
  • Effective Communications and Conflict Resolution
  • Supporting the Product in Market

AppStoreHQ surveyed over 25 published iPhone developers of varying sizes to understand where problems typically arise in each of these areas, and to identify solutions that can help turn ‘nightmare’ projects into ‘dream’ engagements for both the developer and the client. The results of this survey are presented below.



Survey Results: How To Hire an iPhone Developer

Question 1: How much experience should a contract iPhone developer have?

Our goal with the survey was to offer a representative sample from the field of established contract developers. The first question we asked of all survey participants was how many unique iPhone applications they had built and shipped for paying clients.

Among the respondents, a small minority (15%) were still working on their first contracts and had not yet released them to the App Store. The bulk of respondents (59%) had released between one and four applications, with a handful having shipped from 10 to 19 apps (7%), and the same number (7% of the total) having released 20 or more client applications each.

The Bottom Line: Your developer should have a portfolio of at least 2-3 published apps similar to the kind you want built to earn your trust.


Question 2: How much should it cost to have an iPhone application developed?

Perhaps the greatest source of misunderstanding between iPhone developers and their clients is the topic of development cost. Creating a successful iPhone app requires a broad range of skills, from visual and interaction design to software development, and often including specialized skills in graphic, video, sound and animation design as well.

Clients unfamiliar with the process are often surprised by both the time and cost required to realize their vision, while developers are frustrated by clients who express a desire for quality but balk when presented with the corresponding cost.

Given the broad range of possible applications and quality levels, it should come as no surprise that our developer group reported a similarly broad range of budgets for their client applications. Most (61%) of applications across the surveyed group were built for less than $10,000, with 29% coming in at or under $5,000 and the balance (32%) between $5,000 and $10,000. But prices can range much higher, with 7% reporting a per-app cost of more than $40,000, 4% between $30,000 and $40,000, and nearly 18% between $10,000 and $20,000

The Bottom Line: While some simple apps can be built for less than $5,000, most cost more - or much more - depending on the complexity of your app and your expectations for quality and specialty production values.


Question 3: How long should it take to have an iPhone app developed?

After cost, the next top-of-mind question for most companies seeking help with their iPhone development is how long it should take to get an app built and released. The wildcard here is the App Store approval process, which is controlled exclusively by Apple and is notoriously hard to predict. For this reason, our time estimates are for the development process up to submission to Apple; expect at least a few weeks more for that last step (and be aware that Apple reserves the right to reject any app outright).

While some projects (19%) were able to go from first handshake to submitted app in 30 days or less, most take a few months of work, with 41% clocking in at 30-60 days, and another 33% requiring 60-90 days for completion. A small minority took even longer, with 4% requiring 120-180 days and another 4% taking more than 6 months to get across the finish line.

The Bottom Line: Expect your app to take 2-3 months to go from idea to App Store approval process, and remember that the last step - Apple’s approval - is entirely out of your (and your developer’s) hands.


Question 4: What can you do to ensure that your iPhone app development project goes smoothly?

Every iPhone app is unique, but our developer group was remarkably consistent when asked to identify the attributes most likely to contribute to a successful app development project.

On a scale from 1 (not important) to 4 (extremely important), the following attributes each received an average rating of 3 or higher, suggesting that a focus on these areas will do the most to increase your odds of success:
  • Realistic budget expectations (3.37)
  • Well-defined project goals (3.33)
  • Clear and timely feedback (3.33)
  • Realistic time expectations (3.19)

The Bottom Line: iPhone development projects are much more likely to succeed when both client and developer agree to clear time, budget and goals expectations up front and stay in close communication about those goals (and any required tradeoffs) as the project goes forward.


Question 5: What are the top reasons why iPhone development projects run into trouble?

We asked developers to list the three most important reasons an iPhone development project goes sour. We then classified these responses into categories to identify the biggest pitfalls. The leading risk areas - and a selection of supporting quotes - are listed below:
  • Scope / Budget Mismatch (54% of participants included this on their list)
    • “Many people see the apps on Apple commercials and think they can be built for $5K”
    • “Unrealistic expectations on the part of the client (primarily cost and time)”
    • “iPhone apps aren’t web apps - they take more time than clients are used to”
  • Unclear Project Definition (50%)
    • “The client didn’t know what they wanted (and didn’t get it)”
    • “Project goals weren’t clear to the client himself”
    • “No defined purposes or main features of the expected app”
  • Developer-Client Communication Problems (46%)
    • “It is important that you and the client know what the project is intended to do and how. If there is not enough transparency with respect to that then the client must have a completely clear vision of what they want. Failing both a project can go horribly wrong.”
    • “Client always requesting new features that were not originally quoted in the scope of work agreement”
    • “Developer and client have different goals/final products in mind”
  • Client Responsiveness (32%)
    • “It is very important for the client to give feedback at various stages so that the app stays on course. Feedback arriving too late in the life cycle can really lead to a lot of changes at late stages in the life cycle”
    • “Either give complete creative control or be prepared to work closely and be very responsive”
    • “Wanting the moon for the price of peanuts can lead to ever-increasing frustration”
  • Lack of Familiarity with iPhone Market Dynamics (7%)
    • “Lack of knowledge (and even ownership) of iPhone platform and device”
    • “Wanting the app to do things the SDK doesn’t allow”
    • “Lack of feeling for the Appstore. Clients don’t get that it’s a completely new market”
The Bottom Line: iPhone projects fail for the same reason other kinds of complex projects do: poor goal definition, mismatched expectations and poor communication, leading to a breakdown in trust.



Question 6: What steps can you take to improve the odds of success with your iPhone project?

Our developer group was similarly clear about the top three steps they and their clients should take to increase the odds of mutual success. Their top recommendations include:
  • Set realistic time and budget expectations (71% of respondents included this on their list)
    • “Apps of the caliber featured in Apple commercials require a significant investment in dollars and marketing”
    • “Understand what can be done on your budget and where you should put your money, cutting other things when needed”
    • “Don’t expect very low hourly rates. If so outsource it to a developing country but don’t complain about quality”
  • Articulate and document clear project goals at the outset (61%)
    • “Be realistic about your expectations and share all your goals - make results specific”
    • “Make sure you know what you want and why you want it”
    • “Define the desired output of the project in every detail”
  • Provide timely and responsive feedback during the project (39%)
    • “Select a single point of contact in the organization who can make iPhone app related decisions”
    • “Commit time to contributing input and thoughts on the application”
    • “Try to give enough and - more important - timely feedback”
  • Communicate frequently and openly about project needs and issues (29%)
    • “Give feedback early and frequently - be open, honest and constructive, but don’t feel you have to spare our feelings”
    • “Be open to opportunities to collaborate with the developer and trust their expertise”
    • “Be open to feedback and actively seek advice and recommendations”
  • Complete and timely delivery of supporting materials  (ideas, content, design elements) (21%)
    • “Make sure we have the right contacts for discussing specifics in all relevant areas - art, content, servers, legal etc.”
    • “Have the content and idea for the application ready before starting the project”
    • “Provide required resources promptly”

The Bottom Line: To make your project go smoothly, set realistic project budgets, timelines and quality expectations based on relevant benchmarks; have a clear sense of what you want your app to do and why; choose a developer you can communicate with and keep the lines of communication and support wide open for the duration of the project.


Question 7: What qualities does a “dream” iPhone app engagement have?

We asked our developers to describe their “dream” client engagement. The comments below are a subset of the responses that represent the general views of the group.
  • “A dream client knows what s/he wants in the app and has great communication skills when timely feedback is needed”
  • “The project plan (milestones, deliverables etc.) is taken seriously by both the client and the developer”
  • “Big enough budget to accomodate their project goals.”
  • “Works closely with the development company to provide the information and materials they need at every step of the process.”
  • “The client has a specific goal or purpose for the application they are wanting and can justify it from a business perspective.”
  • “Understand up front that marketing the application is critical in driving downloads; that just publishing an app on the App Store won’t result in immediate downloads.”

If there was one comment that captured the views of the entire group on this question, it was the following:

    • “We’ve worked well with two types of clients. The first type has a very specific app in mind and they provide everything to us - wireframes, graphics, specific text… and we implement it exactly as they want. The second type has a very basic idea and provides nothing to us - just the end goal - and we brainstorm and give them frequent updates and we implement as we want using our best judgement and experience. Both work well. The challenge is when you have someone who is a #1 but thinks they are a #2 customer.”


Question 8: What does a “nightmare” iPhone app project look like?

Finally, we asked our group to describe their worst nightmare project experiences. A representative sample of their replies is included below:
    • “An individual with a ‘great idea’ looking to develop an app at little to no cost (usually with a revenue share as an incentive to the developer)”
    • “A client who has no clear idea of what the application should do but wants it done dirt cheap and completed yesterday”
    • “Expects work to be done very quickly while being slow to approve designs and test beta versions. Expects the quality of the work to match his vision and not his budget. Expects the product to match his vision and not what he describes his vision to be. Asks for many small changes here and there without expecting to be charged extra.”
    • “Needs an app for next week, must be fun and under $5,000”

Directory of Survey Participants (in order of survey response)

Sprella, Pivotal Blur, Jony Cree, Copper Starfish, Nicolinux, Oxagile, Rarebyte,  aMobileFuture, Seagull Systems, R.P.A. Tech,  J2Ke, Guerillapps,  Cory Kilger, BluMtnWerx,  ArcTouch, FV iPhone Apps, Vioxon,  sendmetospace, INCOMUM Design/Brainjuice, Nichols Solutions, Atomic Powered, Yellow Monkey Studios, OpenShadow,  Tap Tapas, TheHyperfactory



Comments (View)
blog comments powered by Disqus
Page 1 of 1