Tous les articles

·4 min de lecture

What the installable app changes for a web game with no account

Ramedex is played in a browser tab first, no download, no account, and the home-screen icon only comes later. A look at this reversed order: what a PWA gives, what it doesn't replace, and when I would go back to a store.

Ramedex starts in a browser tab. You open the link, the map loads with the trains around you, and you catch one. Nothing was asked of you beforehand. No download, no account. The game gives you something before asking for anything.

The installable app and the absence of an account extend that choice, each kicking in at its own moment: commitment comes after use. It's the reverse of a classic app's path, and it's what makes a web game shareable with nothing more than a link.

What the icon adds

In code, an installable web app starts with a manifest. Heavily simplified:

{
  "name": "Ramedex",
  "start_url": "/",
  "display": "standalone",
  "icons": [
    { "src": "/icone-512.png", "sizes": "512x512" }
  ]
}

With display: "standalone" , the game starts without an address bar, in its own window, with its icon on the home screen and its own card in the app switcher. It looks like an app, and as far as you can tell, it is one. The exact criteria that trigger the install prompt change from browser to browser and version to version. The manifest does most of the work.

Another pleasant consequence: the installed version and the browser version are exactly the same code, served from the same address. There's no web demo on one side and a real app on the other to maintain. On the developer side, the barrier is just as low. No store account to pay for, no review queue. Everything fits in one file, shipped with the rest of the site.

What this doesn't give me is a channel. No store page, no ratings, no place where someone might stumble on the game by accident. And the icon lands on the screen because the player put it there, at the moment they decided to. As a side effect, without store review, a release is just a deployment.

Commitments in reverse order

A classic app lines up its asks at the beginning. You discover it on a store, you install it, you create an account, and only then do you see what it's worth. Every step loses people, so every step becomes a funnel to optimise, with rates to track.

On Ramedex, the order is flipped. The link stands in for the store, the tab for the installation, and the first game for the demo. You play first. If you come back, you can add an icon to your home screen. If you want to keep your cards, you create an account, with a link or a six-digit code sent by email. No password, so nothing to forget.

The first permission you run into is location. You can't catch the trains passing within twelve kilometres of you without knowing where you are. Rare-train alerts go through notifications, which you only turn on if you want them.

The link also changes what sharing means. Dropped into a conversation, it opens on the spot, on any phone. Trying it costs nothing, not even a download, whereas a native app has you install the whole package even for thirty seconds of curiosity.

I followed that logic into card sharing. On Firefox Android, image sharing doesn't work: the image becomes a public page with a preview, and that page's link is what goes into the share menu. Everywhere else, the image is prepared as soon as the card opens, showing "Preparing…" until it's ready, with a second tap if the browser refuses.

What this doesn't solve

PWA installation stays well hidden. On iOS, it goes through the share button and then an Add to Home Screen option, and nobody guesses that without help. On Android, depending on the browser, it's an entry in a menu, sometimes a more visible prompt, sometimes nothing at all. I control neither the timing, nor the wording, nor whether the option exists. If I want players to install the game, I have to explain it myself, with words that change from one browser to the next. Doable, but it's work around a problem the stores solved a long time ago.

Not being on a store also costs credibility. In a browser, the game looks like a web page, and the icon doesn't change that, since it only exists on the screen of whoever put it there. I'm not claiming it replaces being on the App Store. But once installed, Ramedex starts from the home screen, like any other app. That helps a little.

When I would do the opposite

Two cases would send me back to the store. First, if the core of the app needed something the browser doesn't provide, like certain hardware access or background use. Second, if the store were the natural channel, because that's where people look for this kind of app, or because you sell it. At work, I build mobile apps with Capacitor, and they go through the stores. For them it's the right path, and the bare-link question never even comes up.

Ramedex is in neither case. The day I need it to be found rather than shared, I'll know where to go. Until then, a link is enough.