Sailcards

Sailcards is a SailfishOS fidelity card wallet. It lists cards with a name, a color, and a code, and shows the barcode/QR code when a card is tapped. It also provides actions to scan (take a picture) a new code and to remove cards. The app is built incrementally and follows Sailfish native UI expectations.

Install from OpenRepos.net via Storeman app: https://openrepos.net/content/amol/sailcards

User experience flow

1. Open the app to a list of cards showing their names in white text on colored tiles.
2. Tap a card to reveal its barcode or QR code for scanning at a store.
3. Use the scan action to take a picture and add a new code.
4. Use the remove action to delete a card you no longer need.

Minimal data model

Each card stores:

• name: Display name for the card.
• color: Card color used for the list tile background.
• code: The barcode/QR code payload.
• code_type: The detected barcode type for rendering (for example qr, ean13, code128).

Notes:

• Names always render in white text for contrast.
• The default color for new cards is a randomly chosen hue that works with white text.

Features

• List cards with name, color, and code
• Tap to show barcode/QR code view
• Scan (take a picture) to add a new code
• Remove cards
• Persist cards across launches
• Sailfish native UI components and navigation
• Reorder cards

Development quickstart

Prerequisites:

• Docker

Commands:

• ./scripts/dev <target> to build and run QML tests in the Docker builder container.
• ./scripts/build <target> to build only.
• ./scripts/test <target> to run QML tests only.
• ./scripts/deploy-device USER@HOST to install built RPMs on a real Sailfish device.
• ./scripts/emulate to build, deploy, and launch the app in a Sailfish emulator on x86_64 hosts.

Notes:

• scripts/build, scripts/test, and scripts/dev run fully inside a Linux/amd64 Docker container.
• Set BUILD_NATIVE=1 to opt out of Docker and run against a locally installed SDK.
• The first run builds a local builder image and installs the Sailfish SDK into .cache/container-home/SailfishOS.
• The Sailfish SDK build engine still runs in Docker, through the Docker socket mounted into the builder container.
• Override the builder image platform with SAILCARDS_DOCKER_PLATFORM=<platform> (default: linux/amd64).
• scripts/emulate is host-native by design and requires an x86_64 host with VirtualBox (VBoxManage) and hardware virtualization support.
• scripts/emulate auto-installs the selected emulator image when missing.
• If emulator startup fails due host dependencies, scripts/emulate prints manual setup guidance instead of trying distro-specific package installs.
• If SDK build engine setup is broken, run ./scripts/reset-sdk --yes to reinstall the SDK.

Examples:

• ./scripts/emulate to use the SDK latest emulator and matching -i486 target.
• ./scripts/emulate --emulator SailfishOS-5.0.0.62 to pin emulator version.
• ./scripts/emulate --skip-build to redeploy and relaunch without rebuilding.

If the Sailfish SDK installer URL changes, override it on the build entrypoint:

• SAILFISH_SDK_INSTALLER_URL=<url> ./scripts/build <target>
• SAILFISH_SDK_INSTALLER_VERBOSE=1 ./scripts/build <target> enables verbose installer logs.

The installer is downloaded into .cache/sailfish-sdk by default.

Roadmap / next steps

• Add validation and duplicate detection for codes
• Add import/export for backups