Make local services feel simple to discover and book.
The product needed to move from open-ended browsing into informed action: choose a category, compare options, trust the provider, and pay.
Fintech service product
Blik
A mobile UX/UI system for discovering nearby services, comparing providers, managing payment methods, and moving from intent to booking with less friction.
- Role
- UX / UI Designer
- Mobile app structure, discovery surfaces, payment flows, interface states, and visual system.
- Focus
- Service marketplace
- Help users find nearby services, compare providers, understand pricing, and move to booking.
- Platform
- iOS product
- A polished mobile experience with light and dark surfaces, map context, and account flows.
- Year
- 2024
- Designed and shipped through 2024 as a Softcode founder-led engagement.
- Duration
- ~3 months
- Roughly a three-month sprint from intent-to-payment flow through hand-off to engineering.
Project arc~3 months - Research, completed
- Personas, completed
- Data, completed
- Refinement, completed
- Done, completed
I shaped the flow from intent to payment.
The UI work connected home discovery, service cards, provider sheets, wallet setup, and account states into one consistent mobile system.
Discovery UX
The home screen acts like a grounded starting point.
Blik’s first job is orientation. The UI gives users a location anchor, clear service categories, and nearby recommendations before asking them to make a decision.
The hierarchy moves from place, to need, to nearby provider so the user never has to start from a blank search state.
Start with where the user is.
Location and map context appear before the product asks for a commitment, making service discovery feel grounded.
Make categories feel tappable.
Service cards use soft color, iconography, and compact labels so users can scan options without reading long descriptions.
Keep recommendations nearby.
The home screen introduces nearby providers as the next step, reducing the distance between browsing and booking.
Provider decision
Comparison becomes the bridge between browsing and booking.
Service detail and provider selection screens reduce hesitation by pairing practical data with a more human moment of trust.
Every option carries a base price before anyone is contacted — Express $89, Basic $139, Detail $229 — with the service location pinned above so comparing never loses its context.
Rating, bio, the insurance line, and a report link are grouped around one button — Send request — which starts the 90-second dispatch to that provider.
One tap from the order action: every provider carries their own liability insurance and is reviewed before approval, Blik mediates disputes — and says plainly that it is not the insurer.
Wallet UX
Payment methods needed to feel secure and easy to edit.
The wallet screens separate setup from saved-method management, so users can add, review, and trust payment options without decoding a dense settings page.
The layout gives Apple Pay, PayPal, and card entry distinct rows instead of hiding payment setup in a generic form.
Payment state is designed to prevent surprises before booking, which is especially important in a local service flow.
Entry forms inherit the same soft system language, so account creation feels like part of Blik instead of a disconnected utility screen.
Two sides of one marketplace
One product, two very different jobs.
Blik only works when both sides trust the middle. Switch between the customer and the provider journey to see how the same system serves each of them.
The customer side is built to remove hesitation: orient first, compare in context, meet the person, then pay in a way that can't surprise you.
Customer · step 1 of 5
Start from where you areLocation is the first thing on screen. Service categories and nearby providers appear before Blik asks for any commitment, so discovery never starts from a blank search box. Booking status lives right here too — down to "payment hold released" when an order is cancelled.Location anchorTappable categoriesNearby providers on the map
Product flow archive
The mobile system behind the service journey.
A compact carousel of the screens that explain the UX: discovery, comparison, provider context, wallet state, and account entry.
Shipped app · Services
The live app today: six categories, two on the way.
A capture from the production build — the Services tab with the current category set, direct Book now entry points, and honest Coming soon states for Handyman and Lawn & Snow.
Empty state · shipped app
When nobody nearby is free, the app says so — and keeps the door open.
A real capture of the no-provider state: a plain explanation, a Search again action, and the customer's location and service kept intact so retrying costs nothing.
Home discovery
Location, services, and recommendations start the journey.
The home screen keeps discovery lightweight: set location, scan service categories, then move into nearby options without a heavy search form.
Dark mode
The same hierarchy survives a darker product surface.
Category cards, map context, and bottom navigation keep the same structure so the product feels connected across visual modes.
Service detail
Category browsing turns into a clear service decision.
The Cleaning detail screen pairs price, distance, map context, and service options so users can compare without jumping between screens.
Provider choice
A provider sheet gives the user context before ordering.
Ratings, distance, price, and a short provider profile are grouped near the action so the next step feels informed, not rushed.
Wallet setup
Payment entry stays focused and direct.
Payment methods are separated into recognizable options, with a clear add-card path and enough visual breathing room for trust.
Payment state
Saved methods make status and choice easy to scan.
The wallet list distinguishes PayPal, Apple Pay, active cards, expired cards, and primary payment state without overloading the screen.
Provider entry · shipped app
Providers get their own door.
A dedicated provider login with a remember-provider-mode toggle keeps the two sides of the marketplace from blurring on a shared device.
Provider onboarding · shipped app
One form builds the whole profile.
Name, contact, photo, a short bio, and the service address — the same fields customers later see on the provider sheet, captured once.
Provider onboarding · shipped app
Providers pick from the live catalog, at its upfront prices.
Services are chosen from the same catalog customers book from, so a provider's listing, the customer's price, and the payout math all start from one source.
Account system
Entry states were designed as part of the product language.
The login and sign-up work established field styling, hierarchy, and error-ready structure before the user reaches the core app.
Marketing site · theblik.ca
The companion website extends the same product language to the open web.
The app shipped first; the website followed as the surface that explains the ecosystem to people who haven't opened TestFlight yet. The two share type scale, blue/lilac accent palette, soft-card hierarchy, and the same micro-stats (98% response, 4.9/5, under-2-minute booking) so the brand reads as one product, not a deck plus an app.
The hero pairs the brand promise (“service booking feel premium”) with three credibility chips (response rate, rating, time-to-book) and immediately surfaces the two real conversion paths — Join TestFlight for end users, Start with Blik for service providers.
Same hierarchy, smaller frame: title, dual CTAs, then the proof chips. No side-scrolling, no hidden value props.
UX process
How the Blik system came together.
The work split into four overlapping phases — research first, then structure, then surface, then validation. Each phase produced an artefact the next phase consumed, so handoffs were lossless and the team always had something concrete to react to.
Discovery & competitive audit
Studied how on-demand service apps (TaskRabbit, Thumbtack, Jiffy, regional cleaners) handled the four hard moments — service discovery, provider trust, wallet setup, booking confirmation — and mapped where each one leaked users. Findings became the problem statement: shoppers abandon when they can't verify the provider quickly and when payment setup feels like a separate journey.
Information architecture & flows
Sketched the four core flows — Discover → Compare → Book → Pay — and pressure- tested each step against the audit findings. Provider quality controls and live dispatch surfaced as system primitives that needed first-class UI, not buried metadata.
Wireframes → high-fidelity → motion
Wireframes in Figma, then a light + dark interface system around a calm blue/lilac palette and a soft-card hierarchy that keeps long-form info readable. Motion was spec'd at component level (provider sheet, wallet drawer, dispatch states) so engineering had real specs, not guesses.
Validation & companion site
Prototype tested with five service-booking customers and three providers; iterated the comparison sheet copy and the wallet add-method flow based on what they got stuck on. The marketing site at theblik.ca followed once the in-app language was stable, so the brand outside the app matched the brand inside.
Outcome
A service app with a direct path to trust.
The Blik interface connects discovery, comparison, booking trust, and payment state into one focused mobile journey.
Good service UX helps people move from “what do I need?” to “I can book this.”
- A direct path from home discovery to category detail
- Provider decisions supported by rating, distance, price, and profile context
- Wallet and account states that make payment feel easier to trust