The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
A mobile engineer who only codes ships features.
A product-minded engineer ships value.
You can build screens.
You can wire APIs.
You can ship features.
And still…
the product feels off.
Mobile product engineering starts earlier.
Before the first component.
Before the first line of code.
It starts with questions like:
How will this feel in someone’s hand?
What habit does this create?
Will this actually be used…
or just shipped?
I prefer working with a product mindset.
Because code doesn’t live in isolation.
It lives inside behavior.
Inside business goals.
Inside real people’s daily routines.
That’s the part I enjoy most.
P.S. Do you think like a developer first…
or a product builder?
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Amazing design!
The first thing I created for LedgerFlow wasn't a screen.
It was a set of questions.
I'm kicking off a new concept project: **LedgerFlow, an accounting and financial management SaaS platform for small businesses, freelancers and independent business owners.
The goal is to design a website that helps visitors understand what the product does, how it helps their business, and why they should book a demo.
But before opening Figma, I needed to understand the business.
So I created a website discovery and brand strategy questionnaire.
It covers:
→ Brand vision and business goals.
→ Target audience.
→ Website goals and user experience.
→ Branding and visual direction.
→ Services and offers.
→ Project direction and logistics.
I want to understand things like:
Who exactly are we designing for?
What problem does the product solve?
What makes it different from traditional accounting software?
What should visitors understand within the first few seconds?
And what would make them confident enough to book a demo?
Because the answers will influence the website's messaging, content, visual hierarchy and calls to action.
You can't design a clear experience when you don't understand what the business needs to communicate.
LedgerFlow is a concept project, but I'm treating the process like a real client engagement.
I'll be sharing the journey from discovery to website structure, UI design and Webflow development.
And if you're building a SaaS product or need a website that communicates your business value clearly, I'm open to website design and Webflow projects.
Let's talk about what you're building. 🤝
Starting with a discovery questionnaire instead of a screen is how good briefs begin, and "explain what LedgerFlow does in the first seconds" is the right goal to design around. Will the answers become a one page brief?