Looking to create a viral strategy for a new mobile app, it seems to make sense for it to be via text message. Any good examples of SMS strategies?

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.

I'm answering your question assuming that you hope to be able to replicate it's own success in your own mobile app. There are a couple of factors responsible for it's growth that are instructive to anyone building a mobile app. "Leveraging the intimacy and privacy of the mobile phone." We now have an *intimate* relationship with our phone like no other device in the history of technology. Every internet company that started before around 2010 has built their core interactions around "the old web" one which was accessed primarily via a browser on a computer. Companies that start with a clean slate, should be building their interactions around how to do whatever the app is supposed to do while leveraging what is unique to people's relationship to their mobile devices. Photo-sharing has become a core part of the way we communicate now. Snapchat built something that provided an experience that leveraged the feeling of privacy and intimacy that is unique to mobile. "Provided an escape from the "maturity" of other online services." Too many parents, aunts, uncles and other "old people" have encroached into the social networks of teens and young people. As a result, they've had a desire to find places to express themselves in places inaccessible by older generations. An important distinction is that it's not just parents and relatives that young people are trying to avoid, but also employers & colleges who are increasingly using "mature" social networks to review applicants. "Leveraged PR even bad PR" The fact that the app got so much press about it being used to sext was perfect PR for the company, as it essentially reinforced the brand experience that it has today. Essentially, "if it's safe enough to send a sext, it's safe for any kind of communication I want to have." And although the safety and security of Snapchat is actually not as advertised, it still enjoys the reputation of having less impact than any primarily web-based service. Building a successful mobile application is one of the hardest challenges to face designers, programmers and entrepreneurs in the history of writing software. Happy to talk to you if you're considering building a mobile app, about what I've learned about the "table stakes" for success.

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.

There is quite a bit of information available online about eCommerce conversions rates. According to a ton of sources, average visitor-to-sale conversion rates vary from 1-3%. This does not mean the Furniture conversions will be the same. The bigger problem is that visitor-to-sale conversions are not a good data point to use to measure or tune your eCommerce business. All business have some unique friction factors that will affect your final conversion rate. It's very important to understand each of these factors and how to overcome them. The best way to measure and optimize is to take a conversion funnel approach. Once you have defined your funnel you can optimize each conversion rate to better the total effect. For example: Top of the funnel: - All web site visitors, 100,000 / month First conversion: View a product page, 50% of all visitors Second Conversion: Add to Cart, 10% of people who view products Final Conversion: Complete Checkout, 80% of people who put items in a cart In this example we see that only 10% of people who actually view products put them in to a cart, but 80% of those people purchase. If you can figure out why visitors are not adding items to their cart and fix the issue to increase the conversion rate, revenue should increase significantly because of the high checkout rate. You can use free tools like Google Analytics to give you a wealth of information about your site visitor and their behavior or there are some great paid tools as well.

I developed and published mobile apps as an individual for several years, and only formed a corporation later as things grew and it made sense. As far as Apple's App Store and Google Play are concerned, you can register as an individual developer without having a corporation. I'd be happy to help further over a call if you have any additional questions. Best of luck with your mobile app!