Xenia rebrand - #17609
Closed
xeniacloud wants to merge 3 commits into
Closed
Conversation
Adapts the canonical Xenia navy gradient (nextcloud#1233/nextcloud#2266/nextcloud#3399) used by the Desktop/Notes rebrands (XNT-44/45/46/34) in place of Nextcloud's blue (#0082C9/#1CAFFF/#007cc2), applied to: - adaptive icon foreground: the "files" glyph is the literal trademarked Nextcloud cloud logo (SPDX LicenseRef-NextcloudTrademarks) - replaced with the Xenia cloud glyph (from nextcloud-desktop's "Xenia Desktop-icon.svg", inkscape:label="files"), not just recolored - adaptive icon background gradient - legacy pre-API26 launcher PNGs (mdpi-xxxhdpi) + ic_launcher-web(-round).png, regenerated from the same shared-geometry SVG as the VectorDrawable so the raster and vector assets can't diverge - splash screen logo (nextcloud_splash_logo.xml) - same glyph, rescaled - splash screen background + primary/primary_dark/color_accent colors (setup.xml) - single-color picks from the 3-stop gradient, same convention as XNT-34's defaultBrand - app_name (setup.xml) - this app has no app_name_long; app_name IS the launcher-visible string (AndroidManifest already references it via @string/app_name, no hardcoded label to change) Deliberately NOT changed: - applicationId / no resValue app_name pattern exists in build.gradle.kts to touch - changing applicationId would break account_type/authority provider identifiers elsewhere in setup.xml and has no precedent in the sibling notes-android/notes-ios rebrands - qa/versionDev flavor icon overrides (separate source sets, not part of the CI-verified assembleGenericDebug build path) - deeper "Nextcloud" strings (ecosystem app names, server product name, placeholders, interop URL schemes) - out of scope for this surface-level rebrand per the ticket REUSE.toml: carved the touched main-flavor PNG paths out of the blanket Nextcloud-trademark annotation into a new XeniaCloud-attributed block (qa/versionDev stay covered by the original block, untouched). `reuse lint` passes clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JCBWnbTpV5Cksc3s7ZLX1M
…ovider/account identifiers Set applicationId to eu.xeniacloud.files (generic/gplay/huawei), plus eu.xeniacloud.files.beta / .qa for the versionDev and qa flavors, so Xenia Files installs alongside the upstream Nextcloud Files app. applicationId alone is not sufficient for coexistence. The account type and the five content-provider authorities are independent string resources in setup.xml, not derived from applicationId. Left unchanged, they would still collide with the upstream app: duplicate provider authorities fail installation outright, and a duplicate accountType breaks the account authenticator between differently-signed apps. Renamed them following the same pattern upstream already uses to keep its own qa/versionDev flavors installable side by side. The manifest, authenticator.xml and syncadapter_files.xml reference all of these via @string, so they follow automatically; no hardcoded authority literals remain in code. Deliberately unchanged: - Java package com.nextcloud.client (1861 package/import decls) and org.nextcloud.providers.cursors -- source packages, unrelated to applicationId; the module namespace is com.owncloud.android. - db_file/db_name/data_folder -- scoped to the app sandbox, cannot collide across packages. - Store URLs in setup.xml, README/docs -- point at upstream listings; Xenia has no distribution channel yet. - Deck/ecosystem package queries -- outbound refs to third-party apps. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GCJHcfUt8oBjcbG8cdKNSz
Member
|
Very likely not what you wanted to do... |
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
2 participants
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.
🖼️ Screenshots
🏁 Checklist
/backport to stable-xx.x🤖 AI (if applicable)