HomeAboutResume
Mobile App Β· 3 Weeks Β· PM & UX Β· Side Project MSIB Batch 5

Go-IKN!: Tourism Gateway for Indonesia's New Capital

East Kalimantan had no dedicated tourism platform β€” travelers relied entirely on friends and social media. I led UX research and design to build a platform unifying attractions, itinerary planning, accommodation, and community guides in one place.

RolePM & UX Designer
PlatformMobile App
Team3 People
SUS Score85.5
Back to Work
01 β€” Overview

A Region Full of Potential, Zero Digital Infrastructure

Indonesia's capital relocation to East Kalimantan created a rare moment: a region rich in natural beauty, growing in infrastructure investment, and completely without a dedicated tourism platform. Travelers navigated entirely through word-of-mouth and fragmented social media posts.

GO-IKN is designed to be the primary guide for anyone exploring IKN Nusantara β€” offering verified information, smart planning tools, and a community layer that no existing app provides for this region.

"I have never come across an app or website related to Kalimantan tourism β€” I usually get information from friends or reading social media." β€” Josephine, Research Participant

02 β€” Empathize

Research: Understanding Travelers and Locals

The team conducted research with 5 individuals β€” a mix of active travelers and native East Kalimantan residents β€” using in-depth interviews to surface both behavioral patterns and emotional attitudes toward tourism in the region.

Research Objectives

Habits & Usage

Analyze user habits when traveling and using existing tourism apps to identify established behaviors.

Pain Points

Identify critical friction points when apps are used to support travel planning in underdeveloped regions.

Trust & Transactions

Understand transaction preferences and what builds trust in booking local experiences digitally.

What the Research Revealed

  • Kalimantan's nature tourism has strong appeal β€” both domestically and internationally β€” but digital infrastructure is far behind
  • Existing apps (Traveloka, Agoda) don't cover East Kalimantan meaningfully
  • Users trust recommendations from people, not algorithms β€” community is a critical trust signal
  • Price transparency is non-negotiable: unclear admission pricing creates anxiety before visiting

User Personas

πŸŽ’
Indra Maulana
20 Years Old Β· Student Β· Samarinda Β· Organized
"The beach atmosphere when camping with college friends is amazing β€” forgetting the city, enjoying a moment close to nature."
Goals
Smooth, well-planned trip with no surprises at the destination
Ticket transactions handled in-app β€” no offline queuing
Single app: no toggling between maps, booking, and info sources
Pain Points
"I often waste time on the road due to confusion about routes and directions."
"Bad experiences with accommodation cancellations at the last minute."
πŸ™οΈ
Indra Yusharis
32 Years Old Β· HRD Β· Balikpapan Β· IKN observer, local resident
"I see firsthand the development of IKN Nusantara β€” I want a digital platform that matches this region's potential."
Goals
Digitize IKN tourism as the region gains national and international attention
Easy access to verified information β€” not just social media rumors and posts
Simple, user-friendly platform that works across age groups
Pain Points
"Admission prices are unclear unless you've already physically visited."
"Many tourist attractions aren't connected to any app whatsoever."
User Journey

Mapping the Emotional Arc

The journey map revealed something counterintuitive: the most critical design moments weren't inside the app β€” they were before the first download (awareness) and after the first trip (loyalty). Trust had to be established before the first tap.

Awareness
Consider
First Use
Test
Loyalty
positive negative curious cautious confused frustrated loyal
What users do
Discover
Hears about Go-IKN from friends or social media posts about IKN Nusantara
Evaluate
Compares features with existing apps β€” checks reviews, screenshots, and scope
Explore
Opens the app, browses attractions and itinerary builder for the first time
Book
Attempts to book accommodation β€” hits the payment flow for the first time
Return & share
Re-uses app for the next trip, shares tips in community, recommends to others
Friction & pain points
Trust gap
No existing app covers Kalimantan well β€” hard to trust a brand-new platform
Info overload
Flat listing with no categories β€” hard to know where to even start browsing
Payment confusion
Too many steps, pricing unclear β€” users abandon before completing a booking
Design opportunities
Community proof
Surface local reviews and traveler photos early to signal credibility
Transparent info
Show pricing and availability upfront β€” before the user commits to exploring
Category nav
Nature / Culture / Education tabs as primary entry β€” not a flat list
Simplified checkout
Fewer steps, total price always visible, one-tap payment methods
Travel log
Trip diary and promo nudges to retain users between journeys

Key insight: Users at the "Test" stage experienced the sharpest frustration β€” payment confusion and mismatched expectations were dealbreakers. Simplifying the payment interface became a design-critical requirement, not just a nice-to-have enhancement.

03 β€” Define

Synthesizing What We Learned

I conduct to categorizing the information into demographics and engagement, we can clearly see how different users interact with travel applications and what their common behaviors are, which will inform the design and functionality of the travel app we are developing.

Demographics
Engagement
Name
Age
Gender
Job
Residence
Habits
App
User 1
Maria Yosephin
22 y.o
Female
Student
Paser
Prepare budget and tools
Traveloka
User 2
Danang Wijanto
20 y.o
Male
Student
Samarinda
Prepare budget and tools
Traveloka, tiket.com, booking.com
User 3
Harlita Fatihah
32 y.o
Female
Employee
London
Prepare place and tools
Traveloka, Airbnb
User 4
Indra Maulana
20 y.o
Male
Student
Samarinda
Prepare budget and tools
Agoda
User 5
Indra Yusharis
45 y.o
Male
Employee
Balikpapan
Prepare time and tools
Traveloka

App features

What they valued & avoided

Worked Well

Accommodation
Transportation
Tour tickets

Pain Points

Route mismatch
Double payment
Cancellation

Requested Next

AI recommendation
Travel organizer
Community
Price range

Tourism preference

Travel style & habits

Preferred Type

Nature tourism
Kids-friendly
City / modern

Travel With

Friends
Family
Solo Traveler

IKN Interest

Very interested
Some visited

Prep Style

Structured planner
Spontaneous

Transaction preference

How they pay & navigate

Navigation

Google Maps
Road signs

Biggest Spend

Accommodation
Transport
Meals

Payment Method

E-wallet
m-banking
Debit
Cash

After analyzing 5 interviews, findings were categorized across three lenses: app feature preferences, interface expectations, and transaction behavior. The clearest pattern: users want power without complexity.

What Users Valued

Feature Requests That Emerged Organically

04 β€” Ideate

Prioritizing with Impact-Effort Matrix

Not everything could be built in 3 weeks. The Impact-Effort Matrix separated "must launch" features from "great for version 2" β€” keeping scope tight without sacrificing the user value that made the product worth building.

🎯 High Impact, Low Effort β€” Build Now

  • Tourist spot categorization by type and interest
  • Simplified payment with fewer decision points
  • Complete information architecture in all core features
  • Multiple payment method options for accessibility
  • Travel log and itinerary organizer in-app
  • Activity reminders and smart notifications

πŸ”¬ High Impact, High Effort β€” Plan for V2

  • Real-time visitor density tracking at attractions
  • AI recommendations by budget, mood, and history
  • Full community travel sharing feed
  • Live chat with verified local guides
  • Accommodation with fully integrated payment rails

Four Core Features Final

πŸ—ΊοΈ

Tourist Attractions

Curated spots with verified info, pricing, and real visitor reviews β€” no more guessing before arrival.

🏨

Accommodation

Integrated lodging near IKN with transparent pricing, availability, and direct booking.

πŸ“…

Itinerary Planning

Smart multi-day planning with route optimization β€” everything in one app, no extra tools needed.

πŸ‘₯

Community Guides

Local knowledge from residents and experienced travelers β€” the kind of insights no algorithm can produce.

Information Architecture

I structured the app architecture to consolidate fragmented tourism services into a single cohesive flow. The goal was to ensure that nature exploration, booking, and community insights are never more than three taps away.

GO-IKN
bottom navigation bar
Home
Headline
Search
Weather
App Services
Tourism
Accommodation
Guide
Itinerary
Orders
In Progress
E-ticket
History
Tourism Map
IKN Map
Tourism Info
Recommendations
Community
Search Group
Join
Group Chat
06 β€” UI Design

From Wireframe to Final Screen

Five core features were built for the MVP. Each design decision was based directly on research findings β€” not assumptions.

Color
#000000
Base
#237A59
Primary
#D4AF37
Accent

Green represents nature and primary actions, while gold is used for promos and rewards β€” reflecting Kalimantan's natural wealth. The black base provides a modern and premium feel.

Typography
Jakarta Sans
Aa Aa
01
Registration
Welcome Screen Β· Registration Form Β· OTP Β· Success state
Go Sign In
Splash Screen
Go Sign In
Register Screen
Registration Form
Registration Form
OTP Verification
OTP Verification
Login Success
Login
Login Success
Home Page
Design Decisions

The flow is split into 3 linear steps (registration form β†’ OTP β†’ login β†’ home). A 6-digit OTP was chosen as it's faster to confirm from mobile notifications compared to email links, which is relevant for mobile-first users.

02
Tourism & Home
Home Β· Destination details Β· Ticket booking
Go-Home
Home
Go-Wisata
Tourism Page
Booking Step 1
Tourism Details
Booking Step 1
Customer Data
Booking Step 2
Payment Details
Booking Step 3
Payment Method
Booking Step 4
Payment Method Confirmation
Design Decisions

Users can enter from the home page and select the tourism service to explore destinations. At the top of the Tourism page, categories like Nature, Culture, and Education are placed directly as filter tabs to make it easier for users to filter places based on their interests without entering a hidden filter menu.

03
Tour Guide
Guide list Β· Profile & reviews Β· Select package
Cari Pemandu
Home
Cari Pemandu
Search Guide
Profil Pemandu
Guide Profile
Detail Paket
Guide Details
Detail Paket
Guide Reviews
Review Pemandu
Select Schedule
Pilih Jadwal
Payment Method
Konfirmasi
Confirmation
Design Decisions

Guide cards on the search page display ratings, trip counts, and specializations concisely to facilitate quick comparisons without opening multiple profiles β€” addressing the pain point of users finding it difficult to distinguish guide credibility. On the detail page, experience information and reviews from other users are prioritized to build trust. The booking process is broken down into separate steps (select schedule to payment) to avoid cognitive overload and ensure price transparency before final confirmation.

04
Community
Explore groups Β· Rule approval Β· Discussion feed
Beranda
Home
Home Komunitas
Community Home
Eksplor Komunitas
Explore Community
Detail Komunitas
Community Details
Ruang Diskusi
Discussion Room
Design Decisions

The Community feature is designed as an interaction hub for visitors, starting directly with quick access on the home page. Users are directed to an organized community ecosystem where group cards display credibility information like member counts and activity levels. The joining flow is made explicit through a landing page displaying community rules to maintain interaction quality and discussion ethics in chat rooms and feeds.

05
Itinerary
Create plan Β· Add activity Β· Travel reminder
Beranda
Home
Daftar Rencana
Plan List
Detail Itinerary
Add New Itinerary
Pilih Tanggal
Itinerary Created
Tambah Aktivitas
Add Notes
Pilih Kategori
Select Category - Equipment
Berhasil
Select Category - Travel
Design Decisions

The Itinerary feature is designed to give users full control over planning their trips in a structured way. Starting from home integration, users can easily create new travel plans and manage daily activities. The key design decision was to separate the activity-adding flow from the plan overview to avoid visual clutter and ensure the flow from date selection to success is linearly arranged so users don't feel overwhelmed when planning a busy schedule.

Interactive Prototype

07 β€” Usability Testing

Validating with Real Travelers

After building the interactive prototype, usability testing with 5 participants validated core assumptions and surfaced two key iteration areas that materially improved the experience before final handoff.

85.5
System Usability Score
5
Participants
βœ“
Iterations Verified

What Worked Well

What Needed Iteration

The Key Iteration: Booking Flow

Before Iteration
Manual Data Entry

Users were required to re-enter their personal details for every booking, creating unnecessary friction and slowing down the conversion process.

After Iteration
Auto-filled Data

Customer data is now automatically retrieved from the user's account profile, allowing for a significantly faster and more seamless booking experience.

08 β€” Conclusion

Three Things Go-IKN Taught Me

Insight 01

Trust is a Design Material, Not a Bonus

In a region with no established tourism digital presence, users needed to feel the app was credible before taking any action. Every verified badge, every community review, and every transparent price display was a trust-building element β€” not just a UI component filling space.

Insight 02

Community is Not an Optional Feature

The community feature was almost cut for time, but testing proved it was the most engaging part of the entire prototype. Users who could share and read local tips felt significantly more confident planning a trip. It became a core product differentiator.

Insight 03

Designing for Range Produces Better Outcomes

Research participants ranged from 20 to 45 years old. Designing for this range forced hierarchy and language decisions that worked across all demographics β€” which ultimately made the product better for every user, not just the median one.