Sharing frontend logic across Web and mobile
Use the membership project to separate domain state from network, storage and device APIs; keep platform verification explicit.
7 min read
Learning log · 29 October 2026
Frontend decisions from recent project changes
Six reading notes on shared logic, asynchronous state, location, media, forms and release behavior.
What was reviewed
The membership project’s shared logic and platform adapter, the counselor attachment component, the public low-code renderer and the two engineering demos. Project commit history and file modification dates guided the selection; this was a targeted source review.
The request-scope and weather fixtures passed 5 and 12 scenarios; the form-schema suite passed 10 tests. No native-device release or full counselor backend acceptance was rerun.
Sources, commands and verification scopeA personal reflection on AI and frontend work
AI coding puts pressure on familiar frontend work. I want to practise using it for small changes that I can understand, review and test. This reflection connects that intention to the six project notes below.
Learning frontend development when AI can write the codeThe six notes
Who owns an asynchronous response?
Separate search ordering, identity changes and page disposal. Check stale success, failure and finally paths.
7 min read
Location fallback and the user’s latest choice
Label device and network estimates, preserve manual city selection and test searches that finish out of order.
7 min read
When is an uploaded attachment ready to use?
Separate transfer, processing and business attachment; track retries and clean up browser media resources.
7 min read
A low-code form starts with a configuration contract
Review schema validation, stable field keys, numeric zero and calendar dates using the existing form demo.
7 min read
Keep a demo safe before its scripts are ready
A real loading race in the engineering demos led to disabled-by-default controls, versioned assets and delayed-script checks.
7 min read
Questions carried forward
Add DTO boundaries to the shared layer; test stale failures within one account; measure memory during file hashing; check location and background/resume behavior on real devices. Each note explains which observations support the question.
Compiled with AI assistance in drafting and translation. Public source links and executable checks are provided for review.