Bisacom @bisacomdev

Product Designer | Design Engineer | Figma, Design Systems, React & Next.js | SaaS, B2B & AI Workflows | Norwich · Remote UK bisacom.dev England, United Kingdom Joined July 2015

Tweets

4K
Followers

1K
Following

4K
Likes

1K

Bisacom @bisacomdev

5 days ago

@OurFavOnlineDoc It is same with the Ghanaian community too

0 0 1 295 0

View Details

Bisacom @bisacomdev

4 weeks ago

I recommend this book to beginners, career switchers and sel-taught designers. Now available on Amazon Kindle and On Paperback bisacom.dev/from-beginner-… #uiuxdesign

0 0 2 26 0

View Details

🚀 My first book, *From Beginner to Hired*, is under review at Amazon KDP—a practical guide to moving from learning Figma to solving real product problems. Join the launch list for a free 30-Day Career Planner: bisacom.dev/#book #ProductDesign #UXDesign

0 0 1 48 0

View Details

Bisacom @bisacomdev

2 months ago

Vehicle breakdowns are stressful. When designing Mobile Mechanic, I prioritised one principle: Help first. AI second. Assistance is dispatched first, with optional AI support while help is on the way. #productdesign #uiuxdesign #mobiledesign #uxthinking

0 0 1 37 0

View Details

Bisacom @bisacomdev

2 months ago

From requesting roadside assistance to tracking repairs and completing payment, this is the normal flow for my Mobile Mechanic app concept. Designed to reduce friction and give stranded drivers clarity at every stage. Explore the case study: bisacom.dev #UI #UX

0 0 0 48 0

View Details

Bisacom @bisacomdev

2 months ago

Less friction upfront. More support afterwards. The experience adapts as the driver’s needs change. Explore the case study: bisacom.dev What would you remove from an emergency flow?

0 0 0 5 0

View Details

Bisacom @bisacomdev

2 months ago

A key design principle: Ask for information when it becomes useful. Before dispatch, request only what is needed to send help. After dispatch, progressively introduce tracking, messaging, optional AI assistance and payment. Progressive disclosure keeps the urgent path clear.

1 0 0 9 0

View Details

Bisacom @bisacomdev

2 months ago

When you’re stranded, every unnecessary question feels like friction. For Mobile Mechanic, I designed the core journey around one principle: Get help moving first. Collect secondary information later. Here’s how that shaped the experience 🧵 #ProductDesign #UXDesign

1 0 0 36 0

View Details

Bisacom @bisacomdev

2 months ago

The result: an experience designed to provide reassurance from request to repair. Good UX doesn’t always remove the wait. Sometimes it makes the wait understandable. Full case study: bisacom.dev What frustrates you more: a delay, or not knowing what’s happening?

0 0 0 4 0

View Details

Bisacom @bisacomdev

2 months ago

That led to 4 design priorities: 01 Clear status 02 Visible ETA 03 Mechanic visibility 04 Continuous communication The opportunity wasn’t just to make assistance faster. It was to make the journey more predictable.

1 0 0 7 0

View Details

Bisacom @bisacomdev

2 months ago

The biggest roadside-assistance problem isn’t always the breakdown itself. It’s uncertainty. While designing Mobile Mechanic, I asked: How might we reduce uncertainty for drivers when they’re already under pressure? Here’s how that shaped the product 🧵

1 0 1 34 0

View Details

Bisacom @bisacomdev

2 months ago

Mobile Mechanic challenged me to think beyond polished screens and design the complete service experience. Explore the full case study: bisacom.dev Research → Strategy → UX/UI → Prototype What would you improve about roadside assistance? #UIUX #ProductDesign

0 0 0 12 0

View Details

Bisacom @bisacomdev

2 months ago

Why “Help first. AI second”? I didn’t want AI diagnosis to delay roadside help. Assistance is dispatched first. AI is optional, helping identify a possible issue and share useful context with the mechanic. AI supports the service. It doesn’t control access to it.

1 0 0 9 0

View Details

Bisacom @bisacomdev

2 months ago

The problem Breaking down is stressful enough. Uncertainty makes it worse: • Long call-centre queues • Little visibility of who’s coming • Uncertain arrival times The design challenge: How might we reduce uncertainty when drivers are already under pressure?

1 0 0 50 0

View Details

Bisacom @bisacomdev

2 months ago

That thinking translated into an experience centred around three things: Fast dispatch. Live tracking. Repair visibility. Instead of making users repeatedly ask “what happens next?”, the interface continuously communicates status and the next action.

0 0 0 3 0

View Details

Bisacom @bisacomdev

2 months ago

The core journey I deliberately kept the critical path focused: Request Help → Confirm & Dispatch → Mechanic Assigned → Live Tracking → Repair & Pay The priority is getting assistance moving quickly, then keeping the driver informed throughout the journey.