xinxinmingde新 欣 明 德
Designs that get used — not just designs that get awards.
A small, founder-led practice. We work alongside teams to take real products from spark to ship — apps, consoles, AI tools, and the long tail of unsexy systems in between.
We don't list clients here.
By choice, not by lack.
Past work spans cloud and security platforms, supply-chain systems, AI products, and consumer apps that have reached tens of millions of users — at companies large enough that you'd recognize them, and small enough that the founders still answered the phone.
Concrete case studies, screenshots, and references are shared after a discovery call, under NDA. We think that's fair to both the work and the teams who paid for it.
What we make 能力
Build new products
0→1 apps, AI features, products that haven't earned their first user yet. From research and product definition through to a shipping interface and post-launch iteration. We design every layer — flow, screen, micro-interaction, the data model underneath, and the trust layer for AI features (how models meet users, what to surface, what to hide).
Fix complex products
B2B consoles, dashboards, SaaS billing, multi-region edge cases — the parts most teams give up on. Onboarding, upgrade paths, empty states, error states, expiry. Backed by research (interviews, heatmaps, A/B, journey mapping), not the loudest stakeholder. International work goes beyond translation: density, hierarchy, and flow adapted to how local users actually work.
Ship as one team
Where it makes sense, the same person who designs the interface ships the code. Native Android (Kotlin / Jetpack Compose), front-end, AI-assisted development. Designs arrive in production unchanged because there's no handoff to lose them in.
Why xinxinmingde 差异
Designs that ship — because the designer also writes the code.
Most studios hand off Figma files. We hand off products. The gap between mockup and production is measured in hours, not weeks. No "the engineer didn't quite get the spacing right." If the designer is the engineer, there's no spec to mistranslate.
Decisions held to data, not vibes.
Heatmap tests, A/B experiments, behavioral analytics, post-launch reviews. Every meaningful design choice is testable, and we'd rather be wrong on data than right on opinion. If we can't show you why a screen exists, we shouldn't have drawn it.
We've worked at every scale.
From shipping a personal app on the Play Store to making decisions for platforms used by tens of millions. We bring both ends of that spectrum — the freedom of a startup and the discipline of a system at scale — to your problem.
Beyond the screen.
Most digital products live inside an interface. When the experience needs to reach into the physical world — sensing, measuring, reacting — we design that bridge as part of the product itself, not as a separate engineering problem afterwards.
How we work together 合作
Project Sprint
For a defined deliverable: a redesign, an onboarding flow, a research sprint, a 0→1 prototype. Fixed scope, fixed timeline, shipped at the end.
Embedded Design
Senior product designer working alongside your team for a quarter or more. Best for ongoing product evolution, weekly cycles, and teams that need a design partner, not a deliverable.
Discovery + Strategy
A focused engagement to map a problem, audit an existing product, or scope a future redesign. The cheapest way to start working together — and to find out if we're a fit.
How we work 方法
Listen
Interviews, surveys, support tickets. We mean it — half the brief usually changes once we actually listen.
Map
Journey maps, IA, competitive teardowns. Find the gap, frame the opportunity. This is where bad ideas die cheaply.
Design
Sketches → wireframes → high-fidelity prototypes with motion. Every screen earns its place.
Validate
Heatmap testing, A/B experiments, behavioral analytics. Decisions held to the data, not the demo.
Iterate
Post-launch retros, follow-up tweaks, weekly metrics review. The day a product ships is the day the real design starts.
As a craftsman — keep learning, stay grounded.
Build slowly. Build the right thing.
以 工 匠 精 神 持 续 学 习 ， 保 持 正 念
Let's build something
Have a product in mind? An interface that needs rethinking? A team that needs a design partner who understands both pixels and production code? Drop us a line — every email is read.
We work with serious teams. Briefs without basic context — who you are, what you're building, rough scope — generally don't get a reply. Thanks for understanding.