Add content regarding Freemium and Summer Sale 2026#176
Open
SailReal wants to merge 3 commits into
Open
Conversation
Contributor
WalkthroughFour new blog posts (English and German) are added: one announcing the Cryptomator Android freemium model (read-only free access, in-app purchase to unlock full features, 30-day trial) and one for the Summer Sale 2026. The Android download pages are updated to link to the Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🧹 Nitpick comments (1)
content/blog/2026-07-01-cryptomator-android-freemium.de.md (1)
47-47: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueUnify compound noun spelling for consistency.
Use either "Lizenzschlüssel-Variante" or "Lizenzschlüsselvariante" consistently. The unhyphenated form matches the earlier "Lizenzschlüsselvarianten" and is preferred for German compounds.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/blog/2026-07-01-cryptomator-android-freemium.de.md` at line 47, The compound noun spelling is inconsistent in this paragraph; update the phrase in the affected blog content to use the same unhyphenated form as elsewhere in the article. Keep the wording consistent with the earlier use of Lizenzschlüsselvarianten by changing the single occurrence in this sentence from the hyphenated variant to Lizenzschlüsselvariante.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/comparisons/tresorit-alternative.de.md`:
- Line 200: The comparison page content has been updated to the new Freemium
model, but the footer still shows an outdated “Stand” date. Update the footer’s
stand-date text in the same comparison page template/content so it reflects the
current revision and matches the new description.
In `@content/comparisons/tresorit-alternative.en.md`:
- Line 203: Update the comparison page’s stale “as of” footer date to match the
new pricing content. Locate the footer/date text in the same markdown page as
the Cryptomator pricing paragraph and change the “Information as of September
2025” wording to the current month/year so the updated comparison reads
consistently.
In `@data/de/for_individuals_faq.yaml`:
- Line 28: The FAQ answer in for_individuals_faq.yaml now describes iOS and
Android as free but read-only, so the next financing entry must be updated to
match the freemium wording. Find the answer mentioning Cryptomator’s funding
model and replace the “paid mobile apps” phrasing with wording about in-app
purchases or mobile unlocks; keep the style consistent with the surrounding FAQ
entries and use the same terminology as the updated answer.
In `@data/de/pricing_individuals_faq.yaml`:
- Line 12: The FAQ answer currently implies that F-Droid is a purchase channel,
which is inconsistent with the later licensing text. Update the wording in the
pricing FAQ entry so that F-Droid is described only as a download/distribution
option, while the Android license key is clearly stated as being purchased and
used via the website; keep the existing APK mention and adjust the sentence
around the download/purchase flow in the pricing FAQ answer accordingly.
In `@data/en/for_individuals_faq.yaml`:
- Line 28: The freemium wording in the free/read-only FAQ entry now conflicts
with the adjacent funding FAQ answer, which still says Cryptomator is funded
through “paid mobile apps.” Update the related FAQ entry in the same section so
it reflects the new freemium model and stays consistent with the answer near the
Cryptomator availability text, keeping the wording aligned across both entries.
In `@data/en/pricing_individuals_faq.yaml`:
- Line 12: The pricing FAQ answer incorrectly treats F-Droid as a purchase
channel and implies the Android license key is obtained through it. Update the
response in the pricing_individuals_faq entry so the flow clearly says users can
download via APK or F-Droid, then buy/use the Android-only license key from the
website, while keeping the Google Play and withdrawal wording consistent.
---
Nitpick comments:
In `@content/blog/2026-07-01-cryptomator-android-freemium.de.md`:
- Line 47: The compound noun spelling is inconsistent in this paragraph; update
the phrase in the affected blog content to use the same unhyphenated form as
elsewhere in the article. Keep the wording consistent with the earlier use of
Lizenzschlüsselvarianten by changing the single occurrence in this sentence from
the hyphenated variant to Lizenzschlüsselvariante.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: fca91a67-ff96-4d48-a72f-cec31d49aa90
⛔ Files ignored due to path filters (3)
static/img/blog/cryptomator-android-freemium-screenshot.pngis excluded by!**/*.pngstatic/img/blog/cryptomator-android-freemium.pngis excluded by!**/*.pngstatic/img/blog/summer-sale-2026.pngis excluded by!**/*.png
📒 Files selected for processing (12)
content/blog/2026-07-01-cryptomator-android-freemium.de.mdcontent/blog/2026-07-01-cryptomator-android-freemium.en.mdcontent/blog/2026-07-01-summer-sale-2026.de.mdcontent/blog/2026-07-01-summer-sale-2026.en.mdcontent/comparisons/tresorit-alternative.de.mdcontent/comparisons/tresorit-alternative.en.mdcontent/downloads/android.de.htmlcontent/downloads/android.en.htmldata/de/for_individuals_faq.yamldata/de/pricing_individuals_faq.yamldata/en/for_individuals_faq.yamldata/en/pricing_individuals_faq.yaml
Refresh the as-of date on the Tresorit comparison pages (DE/EN) and reword the funding FAQ entries so they match the new mobile freemium model. Addresses CodeRabbit review on PR #176.
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
1 participant
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.
No description provided.