HANYA IDE
Ada sebuah ide — tapi tidak ada awal yang jelas.
Konsep ada tanpa fitur dan layar yang konkret.
NEWON STUDIO · DIGITAL DESIGN PRODUCT DESIGN
Ubah sebuah ide
menjadi produk yang benar-benar bisa digunakan orang.
Kami tidak langsung memindahkan daftar fitur ke layar.
Kami memulai dari masalah pengguna dan nilai inti yang harus diberikan produk — kemudian melakukan prioritas desain, struktur produk, alur, antarmuka, dan MVP yang dapat diuji sebagai satu pengalaman.
Bukan sekedar produksi layar —
sebuah proses desain produk yang menentukan apa yang harus dibangun dan bagaimana orang akan menggunakannya.
OVERVIEW
Produk yang kuat dimulai dengan masalah yang jelas —
bukan dengan berapa banyak fiturnya.
Kegagalan paling umum saat membangun sesuatu yang baru adalah memasukkan terlalu banyak fitur.
Bahkan ide yang kuat menjadi berantakan tanpa kejelasan tentang apa yang harus dibangun pertama, apa yang harus dipotong, dan di mana pengguna harus mulai.
Desain Produk dimulai sebelum UI. Kami menentukan masalah siapa yang kami selesaikan, memprioritaskan kasus penggunaan dan fitur, lalu mengubahnya menjadi layar dan alur.
Desain Produk Newon mengikuti Problem → Product Structure → Core Flow → MVP → UI → Validation.
Jelaskan ini sebelum layar.
- Masalah
- Tujuan Produk
- Nilai
- Struktur Fitur
- Prioritas
- Ruang Lingkup MVP
- Alur Inti
- Validasi
PROBLEMS
Desain Produk membantu dalam situasi seperti ini.
TERLALU BANYAK FITUR
Terlalu banyak fitur terasa penting.
Semua terlihat penting — ruang lingkup MVP tidak pernah tercapai.
TIDAK ADA NILAI INTI
Nilai inti tidak jelas.
Penjelasan panjang, tetapi tidak ada alasan satu kalimat untuk menggunakannya.
PRODUK KOMPLEKS
Struktur fitur terlalu kompleks.
Navigasi dan alur rusak saat fitur terus bertambah.
MEMBANGUN SEBELUM MEMVALIDASI
Pembangunan dimulai terlalu awal.
Implementasi dimulai sebelum masalah dan alur inti jelas.
MEMBUTUHKAN MVP
Anda membutuhkan MVP dengan cepat.
Tentukan cakupan minimum yang dapat membuktikan nilai inti sebelum produk lengkap.
DESAIN ULANG
Pertumbuhan melebihi struktur asli.
Fitur dan pengguna baru membutuhkan arsitektur produk yang lebih jelas.
KETIDAKSELARASAN TIM
Produk, desain, dan engineering membayangkan produk yang berbeda.
Ketidaksesuaian prioritas menyebabkan pengerjaan ulang yang berulang.
PRODUCT DESIGN PRINCIPLES
Principles behind strong product design.
PROBLEM FIRST
Problem first
Define the user problem before features.
VALUE
Value
Make the strongest reason to choose the product clear.
FOCUS
Focus
Early products prioritize features that deliver core value.
USABILITY
Usability
People should understand structure and the next action.
TESTABILITY
Testability
Design for learning — not one-shot perfection.
SCALABILITY
Scalability
Structure should hold after MVP as features grow.
FEASIBILITY
Feasibility
Consider build complexity and realism with design.
BUSINESS FIT
Business fit
Connect experience to core business goals as well as user value.
WHO IT'S FOR
Dibangun untuk proyek seperti ini.
- 01
Teams turning an app idea into a real product
- 02
Startup MVPs
- 03
SaaS products
- 04
AI services
- 05
New mobile apps
- 06
New web apps
- 07
Existing product redesigns
- 08
Products overloaded with features
- 09
Teams that need a smaller MVP scope
- 10
Projects that need shared product/design/dev criteria
- 11
Teams adding features into an existing product system
- 12
Startups that need a testable first product shape quickly
WHAT WE DO
Pekerjaan yang kami jalankan pada proyek ini.
DEFINISI MASALAH
Definisi masalah
Perjelas masalah inti pengguna yang harus diselesaikan oleh produk.
TUJUAN PRODUK
Tujuan produk
Tentukan hasil yang harus dicapai pengguna.
DEFINISI PENGGUNA
Pengguna inti
Siapa yang paling membutuhkan produk.
KASUS PENGGUNAAN
Kasus penggunaan
Kapan, mengapa, dan dalam situasi apa orang menggunakannya.
STRUKTUR FITUR
Struktur fitur
Mengatur fitur dan bagaimana hubungannya.
PRIORITAS
Prioritas
Harus ada / sebaiknya ada / nanti.
CAKUPAN MVP
Lingkup MVP
Tentukan apa yang harus disertakan dalam versi pertama untuk memberikan nilai inti.
ARSITEKTUR INFORMASI
Arsitektur informasi
Hubungkan fitur dan konten ke dalam struktur produk.
ALIRAN PENGGUNA
Aliran pengguna
Rancang tindakan dan layar untuk tujuan inti.
WIREFRAME
Wireframe
Ubah fitur dan hierarki menjadi struktur layar.
UI PRODUK
UI Produk
Rancang antarmuka dengan memperhatikan merek dan kegunaan.
PROTOTIPE
Prototipe
Hubungkan aliran utama untuk meninjau pengalaman produk.
PENYERAHAN
Penyerahan
Kemas struktur produk dan kriteria desain untuk pembangunan.
PRODUCT TYPES · PATH
Many digital product types —
new builds and redesigns.
Types do not share one fixed price or scope — quotes follow project scale.
Redesign does not always mean rebuilding everything. By scope, we can improve specific features or core journeys.
NEW PRODUCT
From idea, problem, and feature structure to MVP and a usable product experience.
REDESIGN
Review usability, feature structure, and core flows — then redesign what needs it.
MOBILE APP
iOS / Android mobile products.
WEB APP
Browser-based products centered on functionality.
SAAS
SaaS products for recurring work and data.
AI PRODUCT
Products with AI input, generation, results, and repeat loops.
PLATFORM
Platforms connecting multiple user types and features.
COMMUNITY
Products centered on people, content, and interaction.
MARKETPLACE
Services connecting buyers, sellers, and related roles.
INTERNAL TOOL
Internal tools for teams and companies.
MVP · PRIORITY · STRUCTURE
Anda tidak memerlukan produk jadi
dari hari pertama.
An MVP is not a rough product — it is a focused product that can test the most important hypothesis.
Prioritization weighs user value, business goals, and build realism together.
Product structure is not a screen list — it defines how features, actions, and information connect.
HARUS ADA
Diperlukan untuk merasakan nilai inti.
SEHARUSNYA ADA
Meningkatkan pengalaman awal — tidak diperlukan untuk v1.
NANTI
Dapat menunggu hingga setelah respons pengguna nyata.
ALIRAN MVP
IDE → MASALAH INTI → LINGKUP MVP → BANGUN → UJI → BELAJAR → ITERASI
NILAI PENGGUNA
Prioritas — nilai nyata bagi pengguna?
PENGALAMAN INTI
Prioritas — diperlukan untuk pengalaman inti?
FREKUENSI
Prioritas — seberapa sering orang akan menggunakannya?
NILAI BISNIS
Prioritas — seberapa terkait dengan tujuan bisnis?
KOMPLEKSITAS
Prioritas — tingkat kesulitan dan biaya pembangunan?
DEPENDENSI
Prioritas — apakah fitur inti lain bergantung padanya?
NAVIGASI
Struktur — area utama dan pergerakan.
ISI · AKSI
Struktur — informasi yang dikelola orang dan tindakan inti.
STATUS · UMPAN BALIK
Struktur — keadaan dan bagaimana hasil dikomunikasikan.
PENGATURAN
Struktur — personalisasi, akun, dan pengaturan operasi.
Early products prioritize the minimum flow that lets people experience core value — not feature count.
STATES · LOGIC · AI · BUSINESS
Real products are more
than the happy path.
In Product Design we reflect key conditions and states in UX structure with build in mind — this is product-logic design, not coding delivery.
AI features can be designed as roles inside the product journey — not only a chat box.
Business-model touchpoints can be designed by scope; we do not guarantee revenue or paid conversion lifts.
Core UI components and design rules can connect by scope; a full design system may be separate.
Prototypes can review navigation, flow length, CTAs, screen links, and blockers before build. Prototype results do not guarantee business success.
EMPTY
No content yet.
LOADING
Waiting on process or data.
ERROR
Something went wrong.
SUCCESS
Action completed.
DISABLED
Unavailable now.
PERMISSION
Permission required.
LIMIT
Usage or plan limit.
OFFLINE
No connection — when the project needs it.
IF FIRST USE
First-time user → Onboarding
IF AUTH
Login required → Authentication
IF NO DATA
No data → Empty + First Action
IF SUCCESS / ERROR
Success → Success Feedback / Error → Error + Recovery
AI JOURNEY
INPUT · CONTEXT · GENERATION · RESULT · REGENERATE · EDIT · TRUST · ERROR · USAGE LIMIT
BUSINESS UX
FREE→PAID · SUBSCRIPTION · PAYWALL · TRIAL · CREDIT · UPGRADE
UI SYSTEM
Color · Type · Spacing · Button · Input · Nav · Card · Modal · State · Feedback
WHAT'S INCLUDED
Termasuk dalam cakupan dasar.
Exact feature count, screen count, flow count, prototype scope, and deliverables vary by project.
- Ulasan Produk / Masalah
- Tujuan Produk Inti
- Definisi Dasar Pengguna
- Struktur Fitur
- Prioritas Fitur
- Ruang Lingkup MVP
- Arsitektur Informasi
- Alur Pengguna Inti
- Key Wireframes
- Antarmuka Produk Inti
- Desain Status Kunci
- Prototipe Dasar
- Serah Terima Dasar
DELIVERABLES
Apa yang kamu terima di akhir.
Actual deliverables may vary with project scope.
DEFINISI PRODUK
Definisi Produk — masalah inti, nilai, pengguna, dan tujuan.
PETA FITUR
Struktur Fitur — fitur utama dan hubungan.
LINGKUP MVP
MVP Scope — fitur inti yang dibutuhkan untuk versi pertama.
ARSITEKTUR INFORMASI
Struktur Produk — bagaimana fitur dan konten terhubung.
ALUR PENGGUNA
Alur Pengguna Inti — jalur end-to-end untuk aksi kunci.
WIREFRAME
Wireframe — layar kunci dan hierarki informasi.
ANTARMUKA PRODUK
Antarmuka Produk Inti — layar produk utama dalam cakupan.
DESAIN NEGARA
Status Kunci — memuat / kosong / kesalahan / berhasil dan status terkait sesuai kebutuhan.
PROTOTIPE
Prototipe Dasar — prototipe dasar untuk alur inti.
SERAHKAN
Serahkan Desain Produk — struktur dan kriteria desain untuk pengembangan.
PROCESS
Bagaimana proyek berjalan.
MENEMUKAN
Memahami masalah
Bisnis, ide, masalah pengguna, dan tujuan proyek.MENDEFINISIKAN
Mendefinisikan produk
Pengguna inti dan nilai yang harus diberikan produk.MENGUTAMAKAN
Mengutamakan
Mengatur fitur dan menentukan cakupan MVP.MENYUSUN
Menyusun
Arsitektur informasi dan hubungan fitur.ALUR
Alur
Membangun perjalanan penuh untuk tindakan inti.WIREFRAME
Wireframe
Mengubah fitur dan informasi menjadi layar.DESAIN
UI Produk
Mendesain antarmuka dengan merek dan kegunaan.PROTOTIPE
Meninjau pengalaman
Menghubungkan alur kunci dan menelusuri penggunaan.MENYEMPURNAKAN
Menyempurnakan
Kegunaan, status, konsistensi, dan kelayakan.SERAHKAN
Menghubungkan ke pembangunan
Menyerahkan struktur produk dan kriteria desain.
FROM PROBLEM TO PRODUCT
Product starts
before screens.
In Product Design, problem → value → feature → experience must be designed before screen production.
People experience a journey, not a feature list: DISCOVER → ONBOARD → ACTIVATE → USE → COMPLETE → RETURN.
PROBLEM
The problem people face
INSIGHT
Why the problem happens
VALUE
Core value the product delivers
FEATURE
Features that deliver that value
FLOW
How people experience the features
INTERFACE
Screens and interaction
TEST
Check user response
ITERATE
Feed learning back into the product
BEFORE → AFTER
What changes when product design is clarified.
BEFORE
Idea without product structure
Every feature feels essential
MVP scope keeps growing
Features change during build
Flows break between screens
Product and engineering interpret differently
AFTER
Clear core problem and value
Prioritized features
Focused MVP scope
Consistent product structure
Connected core user flows
A concrete, buildable product definition
SCOPE DIFFERENCE
Product Design vs App UI/UX,
and design vs development, differ.
Product Design fits idea-stage work or when prioritization and MVP must be defined first. App UI/UX fits when product structure and features are already clearer. Scopes can combine by project.
This product is design only. Development, servers, and store launch are not included — quoted separately through Newon Business MVP / BUILD when needed.
PRODUCT DESIGN
Starts with what to build — problem, goal, prioritization, MVP scope, structure, core flow, UX, UI.
APP UI/UX
Goes deeper on how to use it — IA, flow, screens, UI, interaction, state, design system.
PRODUCT DESIGN (SCOPE)
Design problem, features, product structure, flows, and interface.
PRODUCT DEVELOPMENT
Implement so the product runs — front-end / back-end / database / API and related build.
Studio Product Design starting price is design only. Live product build continues through Newon Business MVP / BUILD with a separate quote.
TIMELINE
Estimated timeline
A basic-scope project typically runs about 1–2 weeks.
Actual timing depends on product complexity, feature count, user types, core flows, screens, prototype level, research scope, and feedback cadence.
PROJECT SCOPE
Harga awal dan cakupan dasar
PRODUCT DESIGN
From ₩1,000,000
Shown price is a starting point for basic scope.
Final quotes shift with product complexity, feature count, user types, core flows, screens, prototype level, and research scope.
Basic scope
- Problem Definition
- Product Goal
- Feature Structure
- Prioritization
- MVP Scope
- Information Architecture
- User Flow
- Wireframe
- Product UI
- Prototype
- Handoff
OPTIONAL
Available when needed — not in the basic price by default.
These items are outside the base scope. Add them only when needed.
- Product Strategy
- Market / Competitor Research
- UX Research
- User Interview
- Usability Testing
- Brand Strategy
- Naming
- Identity
- Logo Design
- Full App UI/UX
- Full Design System
- Web Design
- Landing Page
- Admin / Dashboard
- Advanced Prototype
- Motion / Interaction
- Illustration / Icon System
- Product Copy
- Development
- Analytics Structure
DEVELOPMENT
When you need product build after design
Studio Product Design is design only — problem, features, structure, flows, and interface.
Live implementation can continue through Newon Business MVP / BUILD as a separate scope.
PRODUCT CONNECTION
Connect idea
to a real product.
Product Design is not a one-and-done artifact — it is the middle link that turns an idea into a launchable structure.
Strategy → Product Definition → MVP → UX → UI → Development → Launch → Learn
After launch, products can keep improving from user response and data. Newon does not guarantee launch success, PMF, or growth.
0104 05
WEB
Design web experience.
02APP
Go deeper on app UI/UX.
03LANDING
Design a single conversion-focused page.
PRODUCT
Current service — define what to build.
CONTENT
Extend the product story through content.
06STUDIO
Explore Studio services.
IMPORTANT NOTICE
Scope notice
Exact feature count, screen count, user flows, prototype level, research scope, deliverables, and revision rounds are confirmed before kickoff.
Product Design covers product direction and experience design. Live development, servers, APIs, databases, and store submission may be separate Development scope.
AI APIs, payments, maps, login, push notifications, and other external services can change in implementation method and cost based on technical conditions and vendor policy.
MVP, prototype, or Product Design does not guarantee user counts, revenue, investment, downloads, conversion, retention, or product-market fit.
Final App Store / Google Play approval is also not guaranteed.
FAQ
FAQ
Yes. After clarifying the problem and core value, we can define features and MVP scope.
No. Early work can define product goals, feature structure, and user flows together.
Product Design starts with what to build — problem, prioritization, MVP. App UI/UX goes deeper on how people use a clearer product.
An early product scope focused on the features required to test the core hypothesis and user value.
Yes. We prioritize by user value, product goals, and build complexity, then define MVP scope.
Yes. We review feature structure and core journeys, then redesign what needs improvement.
No. Studio Product Design starting price does not include development. Implementation is quoted separately through Newon Business MVP / BUILD.
By scope, we can package key flows, screens, and basic handoff. Exact deliverable level is confirmed before contract.
User interviews, UX research, or usability testing can be added by scope.
Yes. Input, generation, results, regenerate, errors, and usage limits can be designed inside product structure.
Yes. Dashboard, subscription, roles, data management, and related structures can be designed by scope.
Screen count depends on features and flow complexity and is fixed at quoting — not unlimited.
Product Design time and Development time are separate. Full launch timing needs product and technical scope.
About 1–2 weeks for basic scope, from ₩1,000,000. Design only — product complexity can change the quote.
START A PROJECT
Mengubah ide menjadi fitur,
dan fitur menjadi satu produk.
Kami mendefinisikan masalah dan nilai inti, mengatur fitur dan alur, dan mengubahnya menjadi produk digital yang bisa Anda bangun dan validasi.