Excited to share that the fac3t logo is finalized 🚀
Also started working on the iOS app in Swift.
Slowly bringing the idea to life, one step at a time.
Excited to share that the fac3t logo is finalized 🚀
Also started working on the iOS app in Swift.
Slowly bringing the idea to life, one step at a time.
The `yaml` package in Dart handles anchors fine for reading, but preserving them on write (for the YAML→JSON→YAML round-trip) is not documented.
If anyone's dealt with `yaml_writer` anchor preservation in Dart, send me a hint.
Folder structure for Fac3t locked in.
Rule I'm committing to: services/ is pure Dart.
Payoffs:
- unit-testable without widget test harness
- easy to extract as an OSS core library later
- keeps me from tangling business logic into UI
Fac3t tech stack, locked:
• Flutter
• go_router
• api_state (my own state package)
• Hive for local storage
• xml + yaml packages for parsing
• Zero network dependencies
One codebase → Android + Windows + Linux. iOS and web later.
The name is Fac3t. Domain: fac3t.live (coming soon)
"Facet" because the product shows the same data from multiple angles — raw, tree, JSON, YAML, XML.
The '3' is a wink. Reads as "facet" out loud, looks like dev in writing.
Logo coming soon.
Why I'm building Fac3t:
Every JSON viewer I've tried either:
- chokes on files over 10MB
- uploads my data to a server I don't control
- buries the basics under schema tools, diff views, 12 codegen targets, and a paywall
I want the opposite. A small tool that does a few things well, stays on my machine, and opens big files without freezing.
Scope for v1: JSON, YAML, XML. Format conversion. Tree view. Search. Edit. That's it.
I'm building Fac3t — a minimal, fully offline JSON/YAML/XML viewer for Android, Windows, and Linux.
No telemetry. No cloud. No "47 features in one sidebar" bloat.
Just a quiet tool for reading and converting messy data.
4 weeks to v1, building in public.
Follow along if you're into Flutter, dev tools, or watching someone ship something small on purpose.