Repository navigation
Lead with the released app, not the beta - #37
Merged
Merged
Conversation
The page still described a closed beta that visitors had to join through a Google Group. The app is on Google Play now, so for almost everyone landing here that was three unnecessary steps in front of an app they could simply install — and a description of the project that was a release out of date. Installing from Play is the primary action. The opt-in flow stays, reframed as what it now is: a channel that gets builds before they are released, for people who want to help find problems, and which you can leave again. The section is called "testing channel" rather than "alpha". The app itself is alpha, unaudited software, and Play's pre-release track is also called alpha; using the same word for both would leave a reader unsure whether the warning above refers to the app or to the channel they are being offered. That warning stays directly beneath the hero. It matters more now than it did during the closed beta, not less: anyone can install this. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The landing page still described a closed beta you had to join through a Google Group. The app is on Google Play now, so for almost everyone arriving here that was three unnecessary steps in front of an app they could simply install — and a description of the project a release out of date.
Changes
Installing is the primary action. The hero button is now Get it on Google Play rather than Join the beta.
The opt-in flow stays, reframed. It is no longer the way in; it is a channel that gets builds before they are released, for people who want to help find problems. The copy says plainly that you can leave and go back to the released version, which the old framing never had to mention because there was nothing to go back to.
Meta and social descriptions no longer say "currently in closed beta".
One naming decision
The section is called testing channel, not "alpha".
The app itself is alpha, unaudited software, and Play's pre-release track is also called alpha. Using the same word for both would leave a reader genuinely unsure whether the warning above the fold refers to the app they are installing or to the channel they are being offered. They are different claims and both matter, so they get different words.
What did not change
The ALPHA · UNAUDITED band stays directly beneath the hero. It matters more now than it did during the closed beta, not less — anyone can install this without joining anything, so the warning is the only thing standing between a casual visitor and trusting an unaudited crypto app with their keys.
Checked
Both pages serve and parse with no unclosed tags, no dangling
#joinanchors remain, and the hero was rendered in a browser to confirm the new call to action reads correctly.