What we built
The [fix]store is the pack marketplace for [fix]net. Think pub.dev meets the Unity Asset Store — a package registry's rigour (versions, changelogs, publishers, honest scores) fused with the richness of an asset marketplace.
Every page is plain HTML that paints instantly. There is no framework, no client-side router, and no multi-megabyte runtime. A build step bakes in snapshot data so the first paint is static; small JS islands freshen specific widgets from the live catalog API.
Why the static-first approach
Speed is non-negotiable. A store page that takes three seconds to show packs is a store page that gets closed. By baking catalog data at build time we get:
- Instant first paint. The HTML is complete before any script runs.
- Works with JS off. You can browse, read changelogs and navigate with JavaScript disabled.
- Robust fallbacks. If a live API call fails, the page still shows something useful — it degrades, it never blanks.
What you can do today
- Browse packs by category, publisher and tag.
- Search the full catalog with filters.
- Read changelogs split into what's new, what broke, and bugfixes.
- Check version histories — every published version, its compatibility range, and its release notes.
What's coming
Release cross-links, a learn hub, ratings, and deep install links that hand off directly to the [fix]net app without copy-pasting a slug. Watch this space — or subscribe to the RSS feed.
The old Flutter store at
store.fixnet.seremains unchanged. This new store runs in parallel; cutover is a separate, explicit decision.