Prototyping for Filipino users: How to build something people here can actually use

Learning goal

Prototypes help you test your idea before building the real thing.

But here’s the catch: what works in the U.S. or Singapore might fall flat in the Philippines.

Local users respond differently to design, language, and features.
If you want your startup to work here, your prototype has to reflect how Filipinos think, decide, and interact with tech.

Why it matters

1. Build for clarity, not perfection
   A prototype is not your final product.
   It’s a learning tool.

Don’t waste time on polish. Focus on:

• Can users understand what the product does?

• Can they complete a task without help?
  If not, simplify again.

2. Use the right tools
   You don’t need a dev team. Use no-code tools to create something testable:

• Figma – for app or web screens

• Canva – for layouts and basic flows

• Google Slides – for clickable walkthroughs
  The goal isn’t to impress—it’s to learn fast.

3. Use local references and tone
   Don’t design like Silicon Valley.
   Design like someone who understands Pinoy behavior.

Tips:

• Use examples users recognize (like GCash or Shopee flows)

• Write in plain Filipino-English

• Skip the stiff corporate tone

4. Test with a tricycle approach
   No need to show 20 users. Start with 3 to 5.

Watch them interact:

• Where do they get confused?

• Do they click where you expect?

• Can they explain the product in their own words?

Write everything down. Then revise.

5. Design for the real world
   Many Filipino users have:

• Older phones

• Limited data

• Unstable WiFi
  Test in real conditions:
  Slow internet, low light, cracked screens, prepaid load.
  That’s how you make something usable in the real world.

Quick checklist

• Your prototype is clear and focused

• Language and visuals feel local

• Tested with 3 to 5 real users

• Tracked behavior—not just opinions

• Improving based on feedback

What to do next / StellarPH tip

Start with just 3 screens.
Focus on solving one real problem clearly.

You don’t need code to create value.
You need clarity, context, and curiosity.