Skip to content

Development plans

What is planned next

This roadmap shows what CollectiGO is building now and what may come next. The approach is deliberate: start with a reliable offline core, then add exchange features and only research optional sync after the foundation is stable.

v1.0

Release date to be announced

In progress

First Android release

The first public version focuses on dependable offline collection management on Android. The goal is a practical daily tool: catalogue real items, organize them clearly, search fast, and keep everything stored locally on the device.

Included in this stage

  • Offline local storage on the device
  • 14 ready-made collection types
  • Custom collection types and flexible fields
  • Color tags for grouping and status
  • Wishlist for wanted items
  • Full-text search and filters
  • 13 interface languages
  • Offline+ with unlimited collections and items

v1.0

Ships with the first release

In progress

Sharing and exchange

Exchange is built and ships together with the first release. Collections move between people and devices without cloud accounts: by encrypted link, by QR code, or by file β€” and nothing is merged until you review it.

Included in this stage

  • Encrypted share links with an optional password
  • QR code transfer between devices
  • Share a collection or profile
  • Friends list for trusted exchanges
  • Inbox for received collections
  • Import and export tools
  • Shared history for sent and received data
  • Review step before accepting incoming items

v2.0

Future

Planned

Optional sync research

This stage is research, not a promise. The goal is to study whether optional sync can exist without breaking the offline-first model, adding unnecessary complexity, or turning accounts into a requirement.

Included in this stage

  • Research only: not committed yet
  • Evaluate optional multi-device sync
  • Explore private backup and restore flows
  • Study conflict handling for edited items
  • Define opt-in setup that preserves offline use
  • Measure storage, battery, and complexity costs
  • Keep no-account workflow as the default path