Agent day
Check in, open Sales or Service, see attendance, return to recent work.
← Back to selected work
CrystalBio project · supporting proof
A field app for agents who need to report work without fighting the software.
CrystalBio is a live mobile workflow used by the client to organize sales, service, attendance, leave, and admin review.
System map
The live system connects field work, admin review, and reporting.
Instead of explaining every screen in paragraphs, this is the simple shape of the product.
Visit capture
Save the real visit first. Add customer, equipment, quote, proof, and notes later.
Admin view
See attendance, leave, agent profiles, entries, reports, and follow-ups.
Live-use reliability
Check-in state, reports, backups, and visible failure points were part of the live-use review.
DecisionThe work was not just making screens. It included deciding what each user should see first, what could wait, and which reliability issues needed review for continued client use.
Workflow
The core loop is short. The details sit behind it.
This is the product logic I kept coming back to while shaping the experience.
1
Start day
Login, check in, location captured.
2
Save visit
Sales or Service Step 1 records the real field action.
3
Add details
Customer, equipment, quote, proof, and office notes.
4
Admin acts
Attendance, leave, follow-ups, reports, and person-wise activity.
5
Use holds
Check-in state, reports, backups, access, and reliability checks.
Decisions
Six product decisions, shown as operating choices.
These are the choices that made the product calmer, safer, and easier to hand over.
Design around the phone.
Daily actions stay visible: Check in, Sales, Service, Leave, My entries, Attendance, Reports.
Split reports into steps.
Quick capture first. Details later, without losing the visit.
Keep admin focused.
Overview, approvals, agents, profiles, and reports each get one clear purpose.
Define live-use quality.
State persistence, reports, access, backups, and clear failures were part of the review criteria.
Use AI with judgment.
Agents helped move fast, but logic, UX, hallucinations, and edge cases still needed review.
Ask production questions.
Storage, monitoring, backups, safer data paths, and hidden debug views came up early.
App screens
Four actual screens in one steady carousel.
The carousel keeps one consistent mockup height and removes the repetitive second visit form.
Agent homeQuick actions make the field loop visible immediately.
AttendanceWork type, location capture, check-in, history, and leave request stay in one place.
Visit updateOne representative visit form is enough; service follows the same interaction pattern.
Admin overviewAdmin sees visits, active agents, leave, follow-ups, and review status.
What became possible
A scattered process became a reviewable product structure.
The project turns field and admin requirements into a live client-used workflow with actual screens, defined responsibilities, and explicit quality checks.
Product senseMoved scattered reporting needs into a clearer agent/admin structure.
Operating judgmentBalanced field constraints, admin needs, and reliability concerns.
AI coordinationUsed agents for speed while checking logic, UX, hallucinations, and failure paths.
CommunicationTurned technical and operational issues into plain product decisions.