Pet follow-up and repeat stays / Interface design
A familiar guest.
A familiar guest.
A separate next stay.
We designed the owner's view around the pet's stay journal, updates from the team and a future visit request.
The journal provides continuity; the next-visit screen handles a new intention.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Pet follow-up and repeat stays
- DESIGN FOCUS
- Keeping pet stay journals and future requests distinct
01 / THE DESIGN DECISION
The journal and the request do different jobs.
We kept the requested return separate from the existing stay record. That lets the experience feel familiar without presenting a pending request as a confirmed booking. The postcard-like treatment gives the journal warmth, while dates and request status retain their administrative role.
02 / THE BUILD
The pages we designed.
The build brings overview, stay journal, from the team and next visit into one workspace.
Stay journal
View the screen ↓From the team
View the screen ↓Next visit
View the screen ↓03 / PROJECT NOTES
Project scope.
We designed and built 4 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.
The gallery shows our rendered pages with identifying details masked.
06 / ON SCREENA closer look.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
4 views Select any view to explore
Have a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.