Until now, the club only existed on the website. On the phone, a group outing was read in the browser, from the link someone had pasted into the group chat. The club now has its own screen in the app: "Club" in the Kennel's modules, or the Club line in Manage, under Team.
What you'll find there
The website's four tabs: Leaderboard, Outings, Trails and Members. If your kennel belongs to several clubs, a picker switches between them.
In Outings, each upcoming outing gives its start, its meeting point, its trail and who's coming. The kennel's owner answers there ("I'm coming", "Maybe", "No"), proposes an outing (title, date and time, meeting point, trail, details) and cancels their own. Any member, whatever their role, taps "Share": the share sheet opens, and the link goes to the club's WhatsApp group.
In Trails, the trails the club's kennels share: tapping one opens its page, with its line, your outings that follow it and its leaderboard. That's also where "Show my times to the club" is set, for that club.
In Members, the owner can leave the club. The founding kennel removes a member and manages invite codes: it creates them, revokes them, and shares a code's link. In Leaderboard, it also sets whether the club's public page shows up in search engines.
Without a club, the owner joins one with the code its founder sent them, or founds one.
The trails list changes too. After your own, it shows, when the phone has a connection, the trails shared in your clubs, with the kennel that made them, then the public trails. And "Log a session" offers your clubs' trails on top of your own.
What others see, and what they never see
Nothing new: the phone only does what the website already allowed.
- Your answer to an outing is read by the club's members, with your kennel's name. An outing you propose is read by them too: title, meeting point, trail, details.
- An outing's link, pasted in the group chat, shows the day and how many kennels are coming. Never the title, the meeting point, the details or the names: those stay with the members.
- Your kennel only appears on a trail's leaderboard, in a club, if you gave your agreement to that club. The agreement starts off. When it's off, the trail's page tells you, and "Set it for this club" leads to the tab where it's set.
- Another kennel's trail shows with its line, never with its pace. For a trail shared in a club, the name of the kennel that made it; for a public trail, no name.
What it doesn't do
- Nothing loads offline. Without a connection, the club screen says so and shows nothing, and a gesture tried offline is refused at once. That's a choice, explained below.
- No notifications. A proposed outing makes no phone ring, as on the website.
- Joining a second club goes through the invite link, which opens in the browser. The screen only offers the code to a kennel that has no club yet, like the website.
- The club's public page, and a shared outing's page, stay website pages. The links you share lead there.
- The public distance leaderboard (
/classement) has no screen on the phone. It's read on the website, including in the phone's browser.
The choices made against the obvious
Online only. Keeping the last reading of the outings on the phone would have let you find the meeting time in the car park, without signal. But an outing cancelled or moved in the meantime would still read there, just as confidently. By the trail, "offline" beats a wrong meeting.
The website's rights, no more. Every role reads the club: an outing's time is useful to the whole team. But answering, proposing, sharing a trail or giving an agreement commits the kennel: only the owner does it, as on the website. The phone offers no button the database would refuse.
Sharing an outing, for any member. It's the only club gesture open to every role: a link only shows what the public page already shows, and it's often the handler, next to the van, who has the group chat at hand.
"Log a session" doesn't wait for the network. Your clubs' trails join the choice when they arrive. Without a connection, the form offers your trails and the reference trails, and the session is saved as before. Nothing you log after an outing should depend on a bar of signal.