Skip to content

Selected work

Planar Lexicon

An offline-first Magic: The Gathering reference and play utility for card discovery, deck building, collections, playtesting, and game tracking.

PlatformsMobile · Web · Desktop · Cloud
Darnfox roleProduct Design · Application Development · Backend & Cloud · Release Engineering
Planar Lexicon card discovery, deck, collection, and play surfaces shown across devices

Audience

Who it serves

Players who want one dependable workspace for finding cards, shaping decks, understanding a collection, and carrying those decisions into play.

The problem

What needed to change

Reference data, deck work, collection state, market context, and live-play tools often fragment across services. Planar Lexicon brings those jobs together without making an account or a reliable connection a prerequisite.

Constraints

What had to stay true

  • Core workflows must remain useful offline and resume cleanly when connectivity returns.
  • Device-local state, optional profile synchronization, and hosted catalog data need explicit ownership boundaries.
  • A growing catalog and media library cannot make discovery or editing feel heavy.
  • Native, browser, and desktop shells must share product behavior without erasing platform conventions.

Darnfox decisions

How the work was shaped

Darnfox centered the product on local-first state, bounded server queries, explicit complete-offline catalog packs, and shared contracts across clients. Complex sync, import, collaboration, and play workflows expose conflicts and unsupported input instead of hiding them behind a generic success state.

Delivered surfaces

What Darnfox handled

  • Cross-platform application and navigation system
  • Card discovery and complete card detail
  • Deck construction, validation, and import
  • Collection, scan, and market workflows
  • Solitaire and multiplayer play utilities
  • Planar Server catalog, media, and profile integration

Current role

Still involved

Darnfox continues to develop the product across client, server, data, accessibility, packaging, and release boundaries.

Building a product that must stay useful offline?

We can help shape the application, data boundaries, and release path as one product.

Start a Project