Where Can I find more clients for iOS Development Jobs?

You can't offer trials or even easily make refunds accessible via in-app purchases. What you can do is actually make manual deposits or write checks back to the users who ask for it. But the purchase behavior associated with in-app purchases really shouldn't require any promise of a refund. In fact, doing so might make people *less* likely to purchase being that you're telegraphing a weak offering. Happy to talk through alternate ways of testing pricing and willingness to pay in a call.

We have been asked this question before and it really depends on the situation and use case. 1. In depends on many factors. 2. Base64 encoding enlarges file sizes by up to 33% 3. If quality is your focus, I recommend URL/URIs. I would love to hear more about this project and provide some more insight. Let me know if you have any other questions. -Steve

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.

Sure, it's correlative for technical reasons, iTunes / AppStore does not provide (yet, might change) a mechanism for that, so 3rd parties have to build their own. I recently discussed with people from Adjust and I was really impressed. HasOffers / MobileAppTracking seems to be a good choice as well.

Well, the biggest cost here wouldn't be in the app, but in the server infrastructure. As usual with connected apps, people often forget they have to be connected to servers. The app itself is just a view to what the servers provide, so it's not the major cost. 20K $ to 100K $ should be enough. On server stuff, I expect it to be a lot more, particularly if you aim for a wide audience (several million $). On a Whatsapp clone, I'd consider: - solutions for performing calls through servers, not that easy. Look at what Twilio provides. WebRTC is an upcoming protocol that will ease that (web & mobile). - solutions for API, IM and user accounts management. Look at StackMob or Parse which are MBaaS (Mobile Backend as a Service). Hope it helps!