VANKPA
Start a project
Founder productMobile Apps · 2026

Vizubly, on the move.

A local home-assistance marketplace needs a faster mobile experience for creating requests, adding task context, coordinating details, and understanding what happens next.

OUR ROLEFounder · Mobile product strategy · UX architecture · Interface design
Vizubly Mobile App detail presentation
PROJECT PRINCIPLEKeep the customer and service team alignedEvidence → Decision → Delivery

Project overview

Founder-led experience.

The Vizubly mobile app extends the founder-led platform into a dedicated mobile workflow. It is designed around the moments where customers need speed and clarity: describing a task, attaching context, coordinating timing, and following progress.

Project
Vizubly Mobile App
Services
Mobile Apps
Status
Founder product
01CHALLENGE

The key decision

A local home-assistance marketplace needs a faster mobile experience for creating requests, adding task context, coordinating details, and understanding what happens next.

02RESPONSE

A practical direction

A focused mobile-app direction that carries Vizubly's request-first model into a compact journey for customers and service operations.

03OUTCOME

What the work made possible.

A connected mobile product system for task requests, photos, scheduling context, status updates, and service communication.

Experience blueprint

Design for real use.

The mobile concept brings Vizubly’s request-first model into the moments where a phone is the most natural tool: photographing the task, adding a short description, confirming location and timing, and checking progress later.

01

Capture in the moment

A customer can begin with a photo and short description while standing in front of the task, reducing recall and unnecessary typing.

02

Clarify progressively

Only the details needed for the current step appear, with additional questions introduced when they improve scope or scheduling.

03

Keep progress legible

Status, messages, and next actions share one timeline so customers do not need to reconstruct the request across channels.

Consulting process

Evidence before
the answer.

The work moves from the situation to the cause, from the cause to a focused response, and from delivery to a measurable next decision.

See the visual story
01
Discover

Choose the right tool

We mapped moments when customers stand in front of a task, photograph it, add a short description, and need a fast answer about what happens next.

WORKING OUTPUTA mobile-context journey grounded in real request behavior.
02
Diagnose

Remove the friction

The analysis focused on unnecessary typing, premature categorization, disconnected messages, and status labels that do not answer the customer’s next question.

WORKING OUTPUTA prioritized set of mobile and service-coordination frictions.
03
Define

Prioritize the release

The direction prioritized camera-led capture, progressive detail, location and timing context, a shared timeline, and clear next actions.

WORKING OUTPUTA focused product brief, flow model, and state architecture.
04
Deliver

Design every state

Thumb-friendly controls, concise language, and a restrained visual system were applied across task creation, detail, communication, and progress views.

WORKING OUTPUTA coherent mobile interface and connected responsive product system.
05
Learn

Track progress

Future learning would examine request completion, missing task context, repeated support questions, and where customers pause in the journey.

WORKING OUTPUTA practical validation plan tied to customer and operational outcomes.

Key decisions

The design choices.

Each decision connects the project’s operating context to a useful, supportable response.

01

Capture first, organize second

Customers can begin with a short description and photos; structure is added progressively as the request becomes clearer.

02

Make status useful

Each state explains what has happened, what is needed, and what the customer can expect next.

Start to finish

Evidence into action.

The mobile system prioritizes camera-led capture, thumb-friendly actions, and clear status states for a faster household-request journey.

01Evidence02Direction03Outcome
An Asian product team comparing Vizubly request-flow screens across several phones.
01 Understand the evidence02 Shape the direction03 Make the result visible

Delivery system

From scope to value.

Select a workstream to inspect the connected delivery system, then switch views to see what the work made possible. Every statement stays within the evidence available for this case.

What was designed01 / 05

Mobile product brief

A focused mobile-app direction that carries Vizubly's request-first model into a compact journey for customers and service operations.

What was designedThe work produced
05 connected signals
05 deliverables04 value signals01 connected system

Continue exploring

Next
projects.

A young Southeast Asian agricultural entrepreneur reviews field observations with colleagues in a healthy rice field.
01
Independent concept · Mobile Apps

HarvestLink Mobile

Farmers and agricultural advisors often spread field notes, seasonal tasks, observations, and consultation follow-ups across disconnected tools.

View case study
Vizubly Operations Analytics project presentation
02
Founder product · Data Analysis

Vizubly Analytics

A growing local-service platform needs to understand request mix, response patterns, service-area demand, and operational friction without turning every available metric into a dashboard.

View case study
Vizubly project presentation
03
Founder product · Web Development

Vizubly

Everyday home tasks can be too small for a traditional contractor, too much to handle alone, and easy to postpone.

View case study

Continue the story

Let’s work it through.

Start with the problem that needs to be solved. We can help define the right next step.

01 · Share context02 · Clarify fit03 · Choose a next step