At UserApp, Robin Y. is known as "Mr. Typo". He will be performing 100 spell checks in 100 days.

I see your point, and many of my later "hacks" has been improved since my first ten. But it also depends on who's definition we use. Most of my "hacks" includes coding (i.e. hacking) and are meant to increase growth. Are they considered growth hacks then? Or must something be "hacked" for it to be called growth hacking?

Actually most hacks are about user acquisition, but there's also retention hacks :)

Yes, that may be true, but the others could still contribute to growth. And it would be really hard (and probably not even good) to come up with 100 "true" growth hacks, and perform them one day after another ;)

Thank you, glad you liked it :) You can follow me here: http://timothy.userapp.io or on twitter: https://twitter.com/timothyej

Believe it or not, but this whole "stunt" (including this deck) hasn't generated that many signups in the long run. The best of my "hacks" would be creating the AngularJS module (http://timothy.userapp.io/post/69135125206/day-25-minimizing...) and then writing about it on Stack Overflow (http://timothy.userapp.io/post/70136752527/day-31-answering-...).

Agree! I do actually work on more deeper problems. At the moment I spend a lot of time creating integrations, improving the documentation and the getting-started guides. As we do get new signups every day, I want more of them to get started and really using UserApp. But to learn how I can improve all that I need feedback, and things takes time. Meanwhile I wait for feedback and test results I spend my time trying to improve conversion rates on the website and to drive more traffic, etc.

Here are a few of my more important "hacks":

[How to guarantee continued operation for an SaaS startup](http://timothy.userapp.io/post/67053194467/how-to-guarantee-...)

[Day 25: Minimizing integration times](http://timothy.userapp.io/post/69135125206/day-25-minimizing...)

[Day 26: Codecademy course](http://timothy.userapp.io/post/69292858355/day-26-codecademy...)

[Day 30: A/B testing getting-started guides](http://timothy.userapp.io/post/70034047713/day-30-a-b-testin...)

[Day 31: Answering questions on Stack Overflow](http://timothy.userapp.io/post/70136752527/day-31-answering-...)

[Day 32: Customer development survey](http://timothy.userapp.io/post/70245235839/day-32-customer-d...)

Thanks for your feedback. Not all of them are UI stuff, e.g the survey, the open-source warranty and the email where I asked why users had canceled. And these was the first 10, now I'm at day 36 and all of them are not about just UI. But I see your point, and the problem is mostly to be able to pull off one hack each day, many would have to be simple and easy to do, and therefore lower quality.

Regarding what actually is a growth hack or not, if it has to be new, none of my 35 hacks are a growth hack. Sharing stuff on social media would be social media marketing, blogging would be content marketing and SEO, and more fundamental "hacks" would be either a part of a business plan or just a marketing strategy.

However, my main goal of many of the things I do is to increase growth, both direct and indirect.

Your growth hacks don't have to be new, certainly not. My point is about communicating in an authentic way and how communication defines the user experience. My bicycle example talks about exactly the same thing and I had two completely different feelings DESPITE being aware of the hard facts.

In my opinion, you under-deliver by making false promises. Your goal should be to over-deliver by giving the user more than he expected. Your slide deck stays entirely the same, it's just about the expectations you set beforehand.

If you're open to suggestions, I'd love to see if you performed two A/B tests on userapp.io:

1. Take different photos of you guys where they look older. You look young. There was once a post on HN about a guy who split tested his profile picture on oDesk or something like that and gave himself an artificial beard in Photoshop. Result: More contacts, more jobs.

I wonder if the photos make a difference in your case and I would be happy to read about the result in one of your slide decks.

2. IMHO you got your coffee-pizza-beer comparison entirely wrong. 650$ is a lot of pizza. Exactly. So the service must provide a heck of a lot of value – more than if I put two coders of my business on a few night shifts to implement the same functionality (or use frameworks that do the same) and supply them with unlimited pizza for the rest of the year. Your goal is to give a feeling that 650$ is a steal by comparing it to something more expensive, not by comparing it to something that is cheaper and valuable as well. I'd kick the comparison altogether. People have their own mindset for comparing prices.

Very nice! This inspired me to create my own Merry Christmas "card" in CSS: http://codepen.io/userapp/full/DbhnB

Merry Christmas!

I know what you mean. Many of the hacks' results may collide. I wonder what a possible solution to that problem could be?

Yes, we are working on that :) The user authentication stuff maybe take a few hours/days to get in place for a experiences developer. However, what we want to focus on is everything else around user management. That's why we are building an add-on store for third-party integrations. Some example cases that we could solve:

* If you have users, you might want to sync them to e.g. MailChimp.

* You would probably want to charge them for using your app, so you would need to integrate a payment provider, calculate payments, creating price plans, etc. UserApp already takes care of all that except the payment processing, which will come as add-ons later.

* Social login (OAuth) to support login from Facebook, Twitter etc.

* Send welcome emails, forgot password emails, etc.

* An admin interface t be able to delete, block, search and manage your users, permissions, etc.

And this is not just for mobile apps. It's for every web, or mobile, app that has users to manage.

Thank you for your feedback!