App Launch Essentials

Do Not Release an App to the App Store Without These Checks

(What Nebula’s Launch at Radisson Blu, Lagos Taught Us)

Launching an app for the first time feels like a finish line. In reality, it’s the starting gun.

When we launched Nebula, Solarsoft’s first product, at the Radisson Blu Anchorage Hotel, everything that could be controlled had already been controlled. The venue was right. The demo worked. People downloaded the app on the spot.

What we didn’t fully appreciate yet was that App Store success isn’t determined by how well your app works on launch night, but by how much control you retain after that night ends.

If you’re shipping without the systems below, you’re not launching — you’re rolling dice.

Social login is where the app truly begins

The first real test of your app is not the home screen; it’s whether users get past authentication without thinking about it. At Nebula’s launch, even tiny delays during sign-up felt amplified because people were installing the app in the room.

This is why social login isn’t a UX enhancement — it’s table stakes. Apple enforces it for a reason: users trust what they recognize, and every unfamiliar step introduces friction.

In practice, that means Apple Sign-In and Google Sign-In should exist before you even think about pushing a build. Email-password flows can exist, but only as a fallback.

Skip this, and two things happen: Apple may reject your app outright, and even if they don’t, users will quietly abandon the flow before you ever get feedback on the product itself.

Once you ship, you lose control — unless you plan for it

The moment Nebula went live, we learned a brutal truth: without runtime controls, every mistake becomes permanent until Apple says otherwise.

This is where Firebase Remote Config stops being “nice infra” and becomes existential. Remote config is how you keep steering after launch — how you force upgrades, disable broken flows, or roll features out gradually instead of gambling on everyone at once.

Without it, bugs live in production longer than they should, users churn while you wait for review approval, and the app’s reputation degrades faster than your ability to respond.

Shipping without remote control is like driving a car with no brakes and hoping traffic stays polite.

Analytics is the bridge between intuition and reality

After the excitement of a launch, the next question always sounds the same:

“So… what are people actually doing?”

If you don’t have analytics in place from day one, that question turns into speculation. At Nebula’s early stage, we realized that feedback alone was misleading — the loudest users weren’t necessarily the most representative.

This is where PostHog becomes essential. It doesn’t just tell you what happened; it shows you where and why. Drop-offs, feature usage, funnel leaks — all visible, all debuggable.

Without this layer, teams tend to over-build, chase ghosts, or double down on features that feel important but aren’t. Growth becomes accidental instead of intentional.

Authentication shouldn’t be another product you have to maintain

As users started returning to Nebula after the launch, a pattern emerged: login friction creates silent churn. Not complaints — disappearance.

Magic links fix this by removing passwords entirely. They turn authentication into a continuation of intent rather than a hurdle. If someone clicks a link, they’re in. No memory required.

When magic links aren’t present, users forget passwords, abandon re-entry, and generate support overhead you didn’t budget for. Over time, that friction compounds into lost retention you can’t explain with analytics alone.

If you plan to charge money, delegate the hard parts

Monetisation is where many otherwise solid apps start bleeding time. Apple subscriptions are full of edge cases — renewals, grace periods, refunds, entitlement mismatches — and all of them surface at the worst possible moments.

Using RevenueCat isn’t about convenience; it’s about abstraction. It gives you a clean mental model of who has access to what, regardless of platform quirks.

Without it, revenue numbers drift from reality, access bugs appear in production, and engineers end up debugging billing flows instead of improving the product. That’s not a growth problem — it’s an organisational one.

If you don’t track where users came from, you can’t grow on purpose

At the Radisson Blu launch, installs came from live demos, WhatsApp shares, and social posts — but attribution was fuzzy.

Deep linking closes that loop. It lets you understand not just that someone installed your app, but why and from where. More importantly, it allows onboarding to be contextual instead of generic.

When deep links are missing, teams default to guessing which channels work, repeat ineffective campaigns, and miss opportunities for virality that were already present.

Apple is predictable — plan for friction, not fairness

Apple doesn’t behave maliciously, but it does behave rigidly. Reviews take time. Rejections are vague. Rules shift quietly.

If your app depends on perfect timing, fragile flows, or last-minute fixes, Apple will expose that weakness. Planning for rejection — technically and emotionally — is part of shipping on iOS.

Ignoring this reality doesn’t speed things up. It only makes delays feel personal.

Sometimes, the App Store shouldn’t be your first step

If Nebula were launched today, the PWA question would surface earlier. Not because PWAs replace native apps, but because they remove friction during learning.

PWAs allow faster iteration, clearer analytics, and zero review delays. For early validation, they often deliver insight weeks sooner than the App Store ever could.

Skipping this option doesn’t make you more serious — it often just makes learning slower.

The real lesson from Nebula

The Radisson Blu launch went well — but the real education started the morning after.

Shipping an app isn’t about confidence at launch; it’s about control, visibility, and recovery afterward. Social login, remote config, analytics, magic links, monetisation tooling, deep links — these aren’t extras. They’re how you stay in the game once real users arrive.