andreaskam

Hehehe good point. I removed it and linked to the HackerNews thread instead as that might be more useful for people.

I have no way of being 100% certain, however I followed the best practises: - Being on a new version of Android - Having an up to date version of Google Play store app - Being on wifi - Having lots of battery and also plugging my phone in to power

Appreciate the reply.

I think you're referring to these guidelines: https://support.google.com/googleplay/android-developer/answ...

We did go through the guidelines to make sure our app would be eligible for auto install. For example our download size is sub 100mb. I can see in Google Play Console that all our installs are Android M+.

There are some factors I can't verify. For example, where can I check what Google Play Store version users are on?

If certain factors make a device ineligible for auto install, then maybe these devices should be excluded from the ad campaign to help ensure developers are getting good value for their ad dollars?

It created such a negative first experience for us on the Google Play store, which is a shame as we'd of been happy to invest in install ads and Google would of made a larger return from us over time. The low quality of support gave us no path to at least share our concerns with Google.

Happy I saved you some $$$

What was painful about pre-registration ads is you don't realise your mistake until you launch your app. Only then do you look at your screen and then go have a cry hahaha.

Be super interesting to read a case study for the App Store and their pre-order ads.

We didn't cap it because we were getting conversions at around $1.36 USD. This is more than we'd normally spend for an install, but we thought it's worth it because it also gives us launch day momentum. Obviously, had we known that actually only 1 in 12 were going to install, we'd of killed that campaign instantly.

We started the pre-registration around 2 months before release and it ran right up until release. The max you can do is 90 days.

Yeah we often think about the free trial vs freemium experience. I really admire apps like FitBod who just let you try out 3 free workouts without needing to commit to a free trial.

Eating healthy is one of the toughest habits to commit to. The benefit of the 7 day free trial is it really pushes people to try it out during those 7 days and see if it's for them. Otherwise you download and think "I'll look at this later" and then never come back to it.

Not saying what we have is perfect and I'm still looking for better options. We're always down to give people a longer trial if they get in touch with us. I get that 7 days won't be enough for everyone.

RE: Instacart integration - we already integrate!

haha it's been my pleasure being a guinea pig. Just wish I could of learned the same lesson for $5k instead of $20k.

All good points. Especially about meal planning being something you're looking to solve right now, not in a few weeks time. Unlike a game, where a few weeks from now you'll still be looking for new entertainment options. Thanks for adding your thoughts, I think they'll be helpful for someone else considering pre-registration for their app.

When they're on their phone it'll show a download button instead :-)

The QR code only appears on desktop.

Fair point. To Google conversion = someone who has pre-registered. That's different to someone actually installing. I never expected 100% of people who pre-registered would install, but having only 8% of people who pre-register go on to download seems kinda wild.

If anyone has any figures for a pre-order campaign on the App Store it would be very interesting to compare the conversion rate.

We felt that getting a lot of traction on the launch day might give us some good momentum in the charts. With hindsight, I'd wish we'd saved our money and spent it after launch, when we could sense check the figures that Google Ads is reporting.

Hope it's helpful for some fellow developers when considering how to promote their app launch :-)

If you look at the first screenshot in the article it shows what the pre-registration page looks like.

It says:

Perks of pre-registering

- Automatic install

Install automatically when it's available

Yeah when I first looked at the analytics in the Google Play Console I thought there must of been some error. Figured it would be a fairly quick thing to sort out with Google support.

If it's a bug then I'm hoping to raise some awareness of it here because the Google support team didn't want to hear about it.

For sure. Live and learn. And hoping to share it here so others can learn from my mistake.

Short version: We used a Google Ads pre-registration campaign to get installs for our app. Google charged us for 16,171 conversions. When we launched, we only received 1,371 installs.

Nibble Apps | Flutter Developer | Remote (Europe) | Full-time

About us: At Nibble Apps our mission is to make healthy eating easy.

Our team is behind one of the most well-loved health apps worldwide, MealPrepPro. MealPrepPro provides users with a healthy weekly meal plan, that adapts to their preferences and goals. The app is regularly featured by Apple and serves a passionate community of tens of thousands of users.

We're bringing our app to Android for the first time and we're looking for a Flutter engineer to join our team.

Learn more and apply: https://nibbleapps.com/flutterdev/

Nibble Apps | Android Developer | Part-time | Remote

Our small, fully remote team is behind some of the best selling food and drink apps in the App Store. We've been featured by Apple, Google and we've received an Apple App of the Year award. We're hiring an Android developer to help us build out our much loved FitMenCook Android app, as well as helping us create new cooking experiences for Alexa and Google Home.

FitMenCook Android: https://play.google.com/store/apps/details?id=com.nibbleapps...

Experience with Google Firebase preferable. You can reach me at andreas@nibbleapps.com

Ah I see! Congrats on the launch today! Will download from direct link instead.

Typed in wifimapper on my iPhone here in the UK. It says no results. Have you checked that?