Problem
Case study / v0.3.0 released frontend prototype; external backend/workers
Zettalogix Migration Suite
A migration-control frontend with a deterministic, network-free workflow for public evaluation.
Target user
Content-migration operators evaluating a control-plane interface.
Solution
React and Electron clients model connections, jobs, progress, history, settings, and reporting; a synthetic session exercises real local state transitions without credentials.
Personal contribution
Built and strengthened the frontend, explicit frontend/backend boundary, synthetic state machine, no-network tests, documentation, deployment evidence, and recruiter path.
Architecture
Boundaries before buzzwords.
- React/Vite operator UI
- Electron wrapper
- Live API adapter
- In-memory synthetic adapter with session-scoped mode
Main workflow
State moves with a reason.
- 01
Enter the clearly labeled synthetic mode
- 02
Inspect connections and migration jobs
- 03
Create and start a job
- 04
Pause and inspect history
- 05
Export a synthetic CSV report
Technical decisions
The trade-offs that define the system.
- Demo mode branches before authentication/network work
- Synthetic data is fictional and deterministic
- External backend ownership stays explicit
Difficult engineering challenge
The baseline frontend depended on external auth and workers; the solution had to demonstrate meaningful migration state without faking production migrations.
Verification
Evidence and boundaries.
Testing
- 7 web tests
- 2 desktop boundary tests
- TypeScript/Vite production builds
- Live Vercel route verified
Security and privacy
- Synthetic mode makes no Supabase, provider, or migration API requests
- Browser env example contains placeholders only
Known limitations
- Migration backend and worker are external
- No successful production migration is claimed
Focused future work
- Add browser smoke and checkpoint/retry views after an owned worker contract exists
Verified demonstration
Rendered product behavior.
Loading video metadata…