In-House App Development Accelerator Guide - Apple
In-House App Development Accelerator Guide - Apple
In-House App Development Accelerator Guide - Apple
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Outsourcing <strong>Development</strong><br />
If you don’t have su∑ cient in-house resources, consider outsourcing all or part of the development<br />
work. Outsourced developers can also present you with a portfolio of their work that could spark<br />
new ideas.<br />
Of course, to be successful, the outsourced team needs a thorough understanding of your project—<br />
everything you’ve determined during the planning process—and regular interaction with you and<br />
your in-house team. Discuss your needs and make sure they understand what your objectives are.<br />
Review the application defi nition statement and carefully review your project details. And be sure<br />
right from the start that you’ve established clear, two-way communication and a process for keeping<br />
in touch.<br />
You need to defi ne the role your outsourced provider will play, just as you would a member of your<br />
internal team. Align their roles and responsibilities to the project plan and timeline so that you can<br />
communicate clearly about which aspects of your project they’ll deliver.<br />
<strong>In</strong>-house team responsibilities<br />
Outsourced developer responsibilities<br />
Requirements Release<br />
Design Code Verification<br />
Some outsourced partners can help you through all elements of the project, from initial requirements<br />
to fi nal deployment. Others may focus only on writing code. It’s good to explore these capabilities and<br />
services with your outsourced provider, whether or not you ultimately contract with them. It can help<br />
you evaluate their strengths and also inform how you shape the relationship.<br />
Planning • Design • <strong>Development</strong> • Deployment<br />
Quick Tip: Selecting an Outside Vendor<br />
• Meet multiple vendors.<br />
• Review existing work, including apps on the <strong>App</strong> Store; note app ranking<br />
and user comments.<br />
• Evaluate skills and capabilities, for example, is all coding done in house?<br />
• Ask for references.<br />
• Disregard one-size-fi ts-all ethic or generic multiplatform approach.<br />
• Focus on UI design, high-quality art, and the app “journey.”<br />
• Discuss maintenance and life cycle of app beyond version 1.0.<br />
• Ask about IT infrastructure experience.<br />
“ We use outside contractors for several di∂ erent pieces.<br />
And it depends really on the need of the app. If there’s a<br />
very specifi c look and feel, we’ll go talk with contractors<br />
who have made things that are similar because we<br />
know that they have expertise in that already. <strong>In</strong> turn,<br />
we can give a higher-quality product to our sta∂ or to<br />
our customers.”<br />
—Todd Schofi eld, Standard Chartered Bank<br />
7