Summary
I’m designing a minimal, friendly desktop-first GUI for Floresta (v0), with a consistent state system and clear mapping to what Floresta currently exposes (sync, peers, services like Electrum/RPC/Metrics, watch-only wallet index, logs/settings).
This issue is the hub for the initial GUI concepts + review.
What’s already designed (Figma frames)
Setup Wizard (First Run)
Home
(Images attached in the issue for quick review.)
Design goals
- Desktop-first layout (sidebar + top status bar) that is still responsive when resized.
- Clear, friendly language for users who don’t understand node jargon yet.
- A consistent state system across some screens:
- READY / LOADING / EMPTY / ERROR / LOCKED
- “Locked” states explain why (e.g., RPC is OFF → console is locked) and link to the fix (Settings).
What I need feedback on (Concept + Approach)
- Does this v0 scope match Floresta’s current reality (florestad + services)?
- Are the terms OK (“Fast Start”, “Backfill”, “Watch-only wallet index”, “Metrics”)?
- Any preference on:
- RPC being off by default always?
- Metrics (Prometheus) being surfaced in v0 or later?
- Any important missing v0 capability I should reflect in UI?
Next steps (after this is approved)
If the direction looks correct, I’ll continue with the remaining v0 screens as separate issues:
- Sync, Peers, Wallet (watch-only), Services (with quick call + endpoints), RPC Console, Electrum Console, Logs, Settings, Help.
Current Available Screen issues

Summary
I’m designing a minimal, friendly desktop-first GUI for Floresta (v0), with a consistent state system and clear mapping to what Floresta currently exposes (sync, peers, services like Electrum/RPC/Metrics, watch-only wallet index, logs/settings).
This issue is the hub for the initial GUI concepts + review.
What’s already designed (Figma frames)
Setup Wizard (First Run)
Home
(Images attached in the issue for quick review.)
Design goals
What I need feedback on (Concept + Approach)
Next steps (after this is approved)
If the direction looks correct, I’ll continue with the remaining v0 screens as separate issues:
Current Available Screen issues