Repository navigation
N/A - #37
Merged
Merged
N/A#37
Conversation
Creem validates that https://bluebubbles.app/pricing resolves, so the route exists now even though Pro is not announced. Hidden deliberately, four ways: not in NAV_LINKS or FOOTER_LINKS so nothing links to it, noindex so it stays out of search if the URL leaks, excluded from the sitemap, and NOT named in robots.txt -- a Disallow rule would publish the path to anyone who reads the file, which is the opposite of hiding it. Launch steps are in a comment at the top of the page. Three plans: $3/month, $30/year, $55 lifetime. The yearly saving is computed from the monthly price rather than asserted, so it cannot drift. The Pro feature list is taken from the server's capability catalogue -- every entry carries minimumTier: .pro in swift/Sources/BBPrivateAPICatalog/CapabilityCatalog.swift. Titles, summaries and macOS minimums are copied verbatim so the page and the server agree, and the source file is cited in src/data/pricing.ts. Nothing about the feature set is invented. Eleven capabilities are Pro: stickers, sticker reactions, pinning, muting, spam and junk, screening unknown senders, FaceTime from a client, Find My, Send Later, polls and conversation backgrounds. The twelve that stay free are listed too, since "Pro adds, it does not take away" is the more important message for existing users. Each feature shows its macOS minimum, which varies from 14 to 26 and materially affects what a subscriber actually gets. /pricing is asserted in verify-build.mjs: it is linked from nowhere, so a build that stopped emitting it would otherwise fail silently and break Creem's validation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Find My is a base-app feature and predates the tier -- it is listed as a working Private API feature in the site's own FAQ compatibility table, so gating it would have taken away something existing users already had. Moves it from the Pro list to the free list, leaving ten Pro capabilities. NOTE: this puts the website ahead of the server. The capability still carries minimumTier: .pro in swift/Sources/BBPrivateAPICatalog/CapabilityCatalog.swift, and the gate needs removing there before this page is published. The summary in swift/docs/SUBSCRIPTION_PLAN.md needs the same edit in that commit: "11 of 23" becomes "10 of 23", and Find My comes out of the gated list. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
FaceTime Calling moves to the top -- it is the most recognisable thing in
the tier and was buried seventh.
Pinning and muting are renamed to say what is actually being sold. The apps
already pin and mute a chat; what Pro adds is that the state syncs across
devices, which the old titles ("Pinning conversations", "Muting
conversations") did not convey at all. They are now "Pinned Chat Syncing"
and "Mute & Snooze Syncing", with summaries that lead on sync and, for
muting, name snoozing explicitly.
This means titles and summaries now deliberately diverge from the server's
capability catalogue, where they are UI labels for the features card rather
than copy for someone deciding whether to pay. The `id` and `macos` fields
are still copied verbatim and remain the link back to the server, so a tier
or macOS-floor change is still a one-to-one edit. The data file explains the
split so nobody "restores" the catalogue strings later.
FaceTime's summary also now says calls can be started, not just answered
and ended, which the catalogue's own action list (dialFaceTime) supports.
Co-Authored-By: Claude Opus 5 <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.
N/A