Loading...
Answers
MenuMy off-shore development team wants my App Store credentials so they can publish the app for me. Is this common practice?
I am nervous to give them access to my all of my credentials. Should I be? Thanks
Answers
_SQUARE.jpg?1626983158)
_SQUARE.jpg?1626983158)
Hi there,
I totally understand your nervousness. Your App Store credentials probably feel like the keys to the kingdom. The question you have to answer is whether or not you trust your offshore development team. If the answer is no, you could use a "remote control" app like TeamViewer (http://www.teamviewer.com/en/index.aspx) to log the developers into iTunes Connect. If the answer is yes, you could add one or more of the team members as Users/Testers in iTunes Connect. I, for one, usually hand over my credentials. After 3 years of iOS development, a couple dozen apps, and probably 10 different programmers, there's been no funny business. Here's one last thing to remember: people selling development services in the form of contract work usually aren't interested in becoming app entrepreneurs. They run small lifestyle businesses, not startups, and they actually stand to lose more than they gain by ripping off a client. Even if they do rip you off, I think you stand to gain a lot more by giving your programmers the benefit of the doubt rather than disrupting their workflow to protect yourself. It all comes back to trust. If you don't trust them, fire them. (Also, be sure they're making daily commits to a code repository on Bitbucket or Github so that you always have the latest version of the code.)
Hope this helps, Austin


Hello -
I would agree that the real question is: what is your level of trust with your outsourcing partner? If you have a good relationship with them I don't see any issue in giving them the credentials.
As a best practice, it's always a good idea to maintain as much control over your assets and resources as possible when dealing with a far away vendor (or any vendor, really). Owning the source control repository, etc. is a great practice.
But, there is a diminishing return on trying to protect yourself from your own vendor. In the end, you'll have more success in outsourcing by investing in a solid partner who you can build trust with so that you don't have to worry about this kind of thing.
If you are dealing with a low-price vendor who's trustworthiness is unknown, you might consider relieving yourself of that stress by working with more reputable vendors. But, if this is just a new relationship and there are no red-flags I'd probably just send the credentials and save everyone some trouble.
TeamViewer is great for things like this, but it's certainly not a great way to build trust with teams so I'd only use it if you are worried about sharing your credentials more than you are concerned with building the relationship.
Probably it will be fine! Good luck - Dave


Hello,
We were a little bit hesitating first couple of times with our customers in terms of asking for App Store credentials and wrote instructions for them since it's really private. But it turned out that most of our customers suggested to share credentials with us not to spend time on publication process that I would not call obvious. Since then we started to ask and work with customers' credentials completely maintaining their accounts.
Like it was mentioned in the previous answer -- outsourcing is a different model of business assuming a bunch of activities aimed at serving client's development process. Having own app that we develop and sell by ourselves I would say that these activities are completely different and requires different skillset that just iOS development. So I'd say that yes it looks to me like a common practice.


It is common; creating and signing builds can be annoying and glitchy for many.
However, you can also create an additional iTunes Connect user with limited privileges exclusively for them to use.
Related Questions
-
What is the generally agreed upon "good" DAU/MAU for mobile apps?
You are right that the range is wide. You need to figure what are good values to have for your category. Also, you can focus on the trend (is your DAU/MAU increasing vs decreasing after you make changes) even if benchmarking is tough. Unless your app is adding a huge number of users every day (which can skew DAU/MAU), you can trust the ratio as a good indication of how engaged your users are. For games, DAU/MAU of ~20-30% is considered to be pretty good. For social apps, like a messenger app, a successful one would have a DAU/MAU closer to 50%. In general most apps struggle to get to DAU/MAU of 20% or more. Make sure you have the right definition of who is an active user for your app, and get a good sense of what % of users are actually using your app every day. Happy to discuss what is a good benchmark for your specific app depending on what it does.
-
I've been working on an app concept for 6 months and built an MVP. Is it better to pay a development firm to build or hire a developer as a cofounder?
I have built two software companies by hiring out the development work. I sold one for a decent sum during the dot com era (circa 1999). I remain a shareholder in the other one. I currently work with amazing development company on behalf of one of my clients. Here are some things to consider. 1. Do you really want to give up equity? If not outsource. 2. How fast do you want to get to market? If sooner than later, outsource. 3. How capitalized are you? If undercapitalized, either outsource offshore (which runs about 20% of US rates), or bring on an equity development partner. I offer a free call to first time clients. Let's chat and I'll give you some great advice from three decades of experience. Just use this link to schedule the free call: https://clarity.fm/kevinmccarthy/FreeConsult Best regards, Kevin McCarthy Www.kevinmccarthy.com
-
Where can I find programmers willing to join a growing mobile start up for equity only?
You won't find anyone worth adding to your team willing to work for equity only, no matter how compelling your product and business is. The realities of the talent market for mobile developers anywhere is such that a developer would be foolish to work only for equity unless they are a cofounder and have double digit equity. Happy to talk about hiring and alternatives to full-time hires.
-
Any opinions on raising money on Indiegogo for an app?
Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.