A restrained architecture concept with a photographic project explorer, category filters, and a tailored enquiry preview. The work leads; the interface gives it room.
Try it: filter the projects and open a project detail.
Open the full website to explore every interaction. Desktop previews are interactive.
These are self-initiated concepts, not client commissions. Business names, prices and testimonials within the demos are illustrative. Photography is credited in each demo.
Beyond the website.
Three native iPhone prototypes, built around sales, travel and meal planning. Explore real screens captured from running builds.
Native SwiftUI · Portfolio prototype
Relay
A sales workspace with a deal pipeline, stage changes, conversation notes and follow-ups that persist between launches.
My role: product design & native development
Running iPhone simulator build. Fictional contacts and deals. Local persistence; no connected CRM backend.
Native SwiftUI · Portfolio prototype
Roam
A quieter travel planner: daily itineraries, saved places, visit tracking and personal trip notes, stored on the device.
My role: product design & native development
Running iPhone simulator build. Sample trip; no bookings or location access. Bundled Unsplash photography.
Native SwiftUI · Portfolio prototype
Mise
Recipes that scale with the table, a weekly meal plan, and a shopping list that combines quantities and tracks what is already bought.
My role: product design & native development
Running iPhone simulator build. Local meal plans and shopping progress; no accounts or cloud connection. Illustrative food photography.
Start with the website. Build on a good foundation.
For a business that needs more over time, the next step should solve a specific problem.
A clear public presence
A responsive website shaped around the business, its offer, and the action a visitor should take.
Tools for the team
A scoped portal or app for representatives: the right information, assignments and follow-ups in one place.
Connected workflows
Explore integrations that reduce repetitive work, with a defined purpose, access rules and usage limits agreed before development.
These are possible project directions, not claims of completed integrations. Requirements, feasibility and costs are established before a build.
A clear process. A project you can follow.
Good work starts with clear expectations. Here is the approach I propose for a client engagement.
Agree the scope
Define the pages, features, price, milestones and responsibilities in writing before the build begins.
Review as it takes shape
Use a working preview to review the design and key interactions. Agree changes before moving to launch.
Plan the handover
Confirm domain and hosting access, source ownership, third-party costs and ongoing support in the project agreement.