feat: restore gallery controls and add mobile access guide - #11
Merged
Merged
Conversation
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.
The hosted gallery now keeps the useful controls from the self-hosted UI: select items for confirmed batch deletion, copy the gallery address, and reveal/copy newly created device tokens again during the current page session. Failed deletions remain selected for retry; tokens remain masked by default and are cleared on logout or page reload. Previously created tokens cannot be recovered from server hashes.
Add a mobile setup page, a standalone web-app manifest and app icons, linked from settings and the sign-in page. The guide covers iPhone/Android home-screen shortcuts and opening the gallery through Shortcuts. Private content is not cached for offline use.
Promote the hosted service in both READMEs, the read-only demo and the product page, with direct usage and mobile instructions. Self-hosting stays the default deployment command.
Validation: typecheck, unit/integration tests, real local Worker/D1/R2 browser regressions (selection/partial failure/token isolation/mobile setup), and Chinese/English demo mobile layout checks.