Tickets & updates

Your tickets drive updates.

Raise a ticket; the developer works on it.

  • Types bugs & features
  • Where in-app or web
  • Replies from the developer
  • Pricing announced at launch
  1. Raise a ticket — in the app or on the web.
  2. Get a reply — the developer reviews directly.
  3. Track it — status and replies in your account portal.
account — your tickets
Bug Preview drawer collapses at narrow widths In progress
Feature Add a keyboard shortcut to swap themes Open
Feature Schedule a nightly cleanup loop Shipped

One place for tickets, states, and replies.

Updates and release terms

  • Release notes record what ships.
  • Update packaging, pricing, and licensing arrive with launch terms.

Raise a ticket

  • Open a ticket from inside the app or on the web — bugs and features share one flow.
  • Describe what you hit or want; it goes straight to the developer.

The developer reviews it directly

  • Tickets feed the roadmap; the developer investigates, replies, and updates status.
  • No guarantee a ticket ships — shipped work appears in release notes.

Track it from your account

What you get

Raise ticketsBugs or features, app or web.
A direct lineTickets reach the developer.
Track everythingState and replies in your portal.
See outcomesShipped work in release notes.

Pricing and licensing are announced at launch — see pricing.

Note
A direct, account-scoped support thread — visible replies and status; no request is guaranteed to ship.