feat(landing): met en avant le téléchargement/ouverture de l'appli sur mobile (#85)
Some checks failed
CI / lint (push) Successful in 2m56s
CI / build (push) Successful in 3m6s
CI / intent-service-test (push) Successful in 4m42s
CI / build-android (push) Has been cancelled
CI / e2e (push) Has been cancelled
CI / test (push) Has been cancelled

Sur un vrai navigateur mobile Android (isAndroidPhoneBrowser(), déjà
utilisé par le ticket #84), la ligne de CTA de la landing page affiche
désormais "Ouvrir dans l'application" comme action PRIMAIRE — plus
utile qu'un compte web puisque l'expérience web n'est de toute façon
pas optimisée mobile (au cœur de ce chantier), et un visiteur avec
l'appli déjà installée peut s'inscrire/se connecter depuis l'appli
elle-même. "Créer un compte"/"Se connecter" sont rétrogradés en
actions secondaires plutôt que masqués : certains visiteurs préfèrent
sciemment le web.

Le clic déclenche attemptOpenNativeApp (tentative d'ouverture du
scheme, repli automatique après le délai) plutôt que d'afficher un
second lien séparé — remplace .landing__mobile-link, ne le duplique
pas. Sur desktop, comportement inchangé (CTA "Créer un compte" toujours
primaire) sauf le lien Android discret, qui pointe maintenant vers
/telecharger (page de repli du ticket #84) au lieu du lien direct
/mobile/download — un seul point d'entrée "obtenir l'appli" pour tout
le site plutôt que deux mécanismes légèrement différents à maintenir
en synchro.

Couverture Cypress : landing.feature étendu avec un nouveau scénario
mobile (UA Android spoofée via onBeforeLoad, même chaîne que le test
unitaire existant d'isAndroidPhoneBrowser dans
mobile-app-redirect.cy.tsx) — vérifie l'affichage du bouton et la
rétrogradation de Créer un compte/Se connecter, SANS jamais cliquer le
bouton réel (son onClick appellerait un vrai window.location.href vers
un scheme personnalisé, qui bloque indéfiniment le runner Cypress/
Electron — piège déjà documenté, la fonction elle-même est déjà
testée unitairement avec un stub injecté). Le scénario desktop existant
est mis à jour pour le nouveau href /telecharger. Suite complète :
biome check, tsc -b --force, build, 145/145 e2e, 71/71 composants —
tous verts.

Closes #85

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Nicolas 2026-09-07 17:34:44 +02:00
parent 23bc19b482
commit 615e320be1
5 changed files with 126 additions and 49 deletions

View file

@ -22,11 +22,17 @@ Feature: Public landing page at the root
When I click the link "Créer un compte"
Then the URL should include "/signup"
Scenario: The landing page offers the Android app download
Scenario: The landing page offers the Android app download, on desktop
Given I am not signed in
When I visit "/"
Then I should see the Android download link
Scenario: A mobile visitor is offered to open the app first, not just a download link
Given I am not signed in
When I visit "/" as an Android phone browser
Then I should see the button to open the app, with sign-up demoted to secondary
And the Android download link should not be shown
Scenario: Another guarded route still redirects a logged-out visitor to sign in
Given I am not signed in
When I visit "/recettes"

View file

@ -1,4 +1,4 @@
import { Then } from "@badeball/cypress-cucumber-preprocessor";
import { Then, When } from "@badeball/cypress-cucumber-preprocessor";
// Landing-page-specific steps. Everything else this feature needs
// (signing in / not, visiting a path, URL and heading assertions) comes
@ -15,19 +15,50 @@ Then("I should see the landing call to action", () => {
.and("have.attr", "href", "/login");
});
// The Android build is distributed as a Forgejo release asset with a stable
// filename (issue #64 builds/attaches it). Points at this API's own
// `/mobile/download` (a plain server-side redirect to the actual latest
// `.apk`) rather than a Forgejo URL directly: Forgejo has neither a
// GitHub-style `/releases/latest/download/<file>` shortcut nor CORS headers
// on its Releases API, so resolving the real asset URL client-side isn't
// possible either way (both verified live). `VITE_API_URL` is unset in this
// environment, so `API_BASE_URL` (see `api/client.ts`) is `""` — same
// origin, hence the bare `/mobile/download` path here rather than an
// absolute URL. We only assert the link is there and points at the right
// path — the redirect target itself is external to the suite.
// Issue #85: desktop only now (see LandingPage.tsx) — routed through
// `/telecharger` (DownloadPage.tsx, issue #84's fallback page) rather than
// linking the Android build's actual `/mobile/download` redirect directly,
// so "get the app" has exactly one canonical destination app-wide.
Then("I should see the Android download link", () => {
cy.get(".landing__hero .landing__mobile-link")
.should("be.visible")
.and("have.attr", "href", "/mobile/download");
.and("have.attr", "href", "/telecharger");
});
// Spoofs a real Android phone Chrome UA via `onBeforeLoad` — the one place
// `isAndroidPhoneBrowser()` (`lib/mobile-app-redirect.ts`) actually reads
// from, so this is the only way to reach the landing page's mobile-only
// branch from a real page visit (Cypress's own Electron browser always
// reports a desktop UA otherwise). Same literal UA string already used by
// `mobile-app-redirect.cy.tsx`'s own `isAndroidPhoneBrowser` unit test.
When("I visit {string} as an Android phone browser", (path: string) => {
cy.visit(path, {
onBeforeLoad(win) {
Object.defineProperty(win.navigator, "userAgent", {
value:
"Mozilla/5.0 (Linux; Android 14; Pixel 7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0 Mobile Safari/537.36",
configurable: true,
});
},
});
});
Then("I should see the button to open the app, with sign-up demoted to secondary", () => {
// Deliberately never clicked here: its `onClick` calls
// `attemptOpenNativeApp()` with the real (production) `openAppUrl`, a
// genuine `window.location.href` to an unrecognized custom scheme — that
// hangs the Cypress/Electron runner indefinitely rather than safely
// no-op'ing (see dev-environment-gotchas.md). The function itself is
// already fully unit-tested with an injected stub in
// mobile-app-redirect.cy.tsx; this only covers LandingPage's own
// conditional rendering.
cy.get(".landing__hero .landing__cta--primary")
.should("be.visible")
.and("contain.text", "Ouvrir dans l'application");
cy.contains(".landing__hero .landing__cta--secondary", "Créer un compte").should("be.visible");
cy.contains(".landing__hero .landing__cta--secondary", "Se connecter").should("be.visible");
});
Then("the Android download link should not be shown", () => {
cy.get(".landing__hero .landing__mobile-link").should("not.exist");
});

View file

@ -1330,6 +1330,7 @@
"lede": "Planifiez vos repas, importez des recettes depuis vos sites préférés, et générez la liste de courses qui va avec — pour tout le foyer, sans y penser deux fois.",
"ctaSignup": "Créer un compte",
"ctaLogin": "Se connecter",
"ctaOpenApp": "Ouvrir dans l'application",
"mobileDownload": "Télécharger pour Android",
"mobileHint": "Fichier .apk à installer soi-même : Android demandera d'autoriser l'installation depuis une source inconnue. Ce n'est pas une version du Play Store, et un compte reste nécessaire."
},

View file

@ -1,8 +1,8 @@
import { CalendarDays, HeartPulse, Smartphone, Sparkles, Users } from "lucide-react";
import type { ReactNode } from "react";
import { useTranslation } from "react-i18next";
import { Link } from "react-router-dom";
import { API_BASE_URL } from "../../api/client";
import { Link, useNavigate } from "react-router-dom";
import { attemptOpenNativeApp, isAndroidPhoneBrowser } from "../../lib/mobile-app-redirect";
import "./landing-page.scss";
/**
@ -22,6 +22,17 @@ import "./landing-page.scss";
*/
export function LandingPage() {
const { t } = useTranslation();
const navigate = useNavigate();
// UA-based, not `useIsMobileViewport()` — same reasoning as
// `attemptOpenNativeApp`'s own doc comment: this decides whether trying
// to open the *native app* makes sense at all (a platform question), not
// whether the viewport is narrow (a resized desktop window shouldn't
// attempt a scheme navigation just because it's a small window).
const isMobile = isAndroidPhoneBrowser();
function handleOpenApp() {
attemptOpenNativeApp({ onFallback: () => navigate("/telecharger") });
}
const features: { icon: ReactNode; key: "planning" | "import" | "health" | "household" }[] = [
{ icon: <CalendarDays aria-hidden />, key: "planning" },
@ -44,7 +55,38 @@ export function LandingPage() {
<h1>{t("landing.hero.title")}</h1>
<p className="landing__lede">{t("landing.hero.lede")}</p>
<div className="landing__cta-row">
<Link className="landing__cta landing__cta--primary" to="/signup">
{/*
* Issue #85: on a real Android phone browser, opening/getting
* the app is more useful than a web account — the web
* experience isn't optimized for mobile at all (the whole
* point of this chantier), and someone with the app already
* installed can sign up/log in from inside it just as well.
* So this becomes the *primary* action, demoting Signup/Login
* to secondary rather than hiding them — some visitors
* genuinely want the browser flow, e.g. to try it before
* installing anything. Desktop is untouched: a scheme-open
* attempt makes no sense there, so Signup stays primary and
* this button doesn't render at all (see the plain `/telecharger`
* link below instead, replacing the old direct-APK link).
*/}
{isMobile && (
<button
type="button"
className="landing__cta landing__cta--primary"
onClick={handleOpenApp}
>
<Smartphone aria-hidden />
{t("landing.hero.ctaOpenApp")}
</button>
)}
<Link
className={
isMobile
? "landing__cta landing__cta--secondary"
: "landing__cta landing__cta--primary"
}
to="/signup"
>
{t("landing.hero.ctaSignup")}
</Link>
<Link className="landing__cta landing__cta--secondary" to="/login">
@ -52,31 +94,19 @@ export function LandingPage() {
</Link>
</div>
{/*
* Secondary action — an account is needed on any platform, so the
* Android build is a discreet link under the CTA row, not a third
* button. Points at this API's own `/mobile/download` — a plain
* redirect straight to the latest release's actual `.apk`,
* resolved server-side (see `mobile.service.ts`) — rather than a
* Forgejo URL directly: Forgejo, unlike GitHub, has no
* `/releases/latest/download/<file>` shortcut (only
* `/releases/latest` itself resolves, to the release's HTML page,
* not a file), and its Releases API sends no CORS headers, so a
* client-side fetch to resolve the direct URL ourselves isn't an
* option either — both verified live. `target="_blank"` so the
* redirect-then-download happens in a new tab, never navigating
* this one away. The hint is honest that this is a sideloaded
* .apk, not a Play Store listing.
* Desktop only — a scheme-open attempt (the mobile button above)
* has no meaning here. Routed through `/telecharger` (the same
* fallback page a failed mobile attempt lands on) rather than
* linking `${API_BASE_URL}/mobile/download` directly, so "get
* the app" has exactly one canonical destination app-wide
* instead of two slightly different mechanisms to keep in sync.
*/}
<a
className="landing__mobile-link"
href={`${API_BASE_URL}/mobile/download`}
target="_blank"
rel="noreferrer"
>
<Smartphone aria-hidden />
{t("landing.hero.mobileDownload")}
</a>
<p className="landing__mobile-hint">{t("landing.hero.mobileHint")}</p>
{!isMobile && (
<Link className="landing__mobile-link" to="/telecharger">
<Smartphone aria-hidden />
{t("landing.hero.mobileDownload")}
</Link>
)}
</div>
<HeroIllustration />
</section>

View file

@ -89,9 +89,17 @@
}
.landing__cta {
// Issue #85: the mobile "Ouvrir dans l'application" CTA is a real
// `<button>` (it runs `attemptOpenNativeApp`, not a navigation), unlike
// every other `.landing__cta` here, which are `<Link>`s — both need to
// look pixel-identical, so `appearance: none` strips the native button
// chrome that `--primary`/`--secondary` below don't already override
// (they redefine `background`/`border`/`color`, but not this).
appearance: none;
display: inline-flex;
align-items: center;
justify-content: center;
gap: var(--space-xs);
padding: var(--space-sm) var(--space-lg);
border-radius: var(--radius-base);
font-family: var(--font-body);
@ -100,6 +108,12 @@
text-decoration: none;
cursor: pointer;
svg {
width: 1em;
height: 1em;
flex-shrink: 0;
}
&--primary {
background: var(--color-primary);
color: #fff;
@ -123,7 +137,9 @@
}
}
// --- Android download (discreet, under the CTA row) --------------------
// --- Android download link (issue #85: desktop only now — a real Android
// phone browser gets the prominent "Ouvrir dans l'application" `.landing__
// cta` button above instead, see LandingPage.tsx) ---------------------------
.landing__mobile-link {
display: inline-flex;
align-items: center;
@ -144,13 +160,6 @@
}
}
.landing__mobile-hint {
margin: var(--space-xs) 0 0;
font-size: var(--font-size-xs);
color: var(--color-text-muted);
max-width: 34rem;
}
// --- Features -----------------------------------------------------------
.landing__features h2,
.landing__preview h2 {