Platon Talent — Mobile App UI/UX
A mobile talent platform I worked on while at Platon — helping people browse and apply for developer & freelancer opportunities, check salary expectations, and keep a polished professional profile. This page collects the screens, reusable components, and the design system from the Figma files, plus a downloadable PDF portfolio.
01 · Overview
A talent platform lives and dies by trust: people want to see real opportunities, understand what they'd earn, and present a credible profile. My focus was making that feel simple and human on a small screen — clear navigation, honest information hierarchy, and reusable UI so the whole product stays consistent as it grows.
This set of designs covers the core experience: the home feed, browse & filter for opportunities, salary expectations, and the developer profile — built on a small but consistent component library.
02 · Problem
Before Platon Talent existed, the process of matching people with work was scattered and manual. Talents struggled to find projects that suited them, and coordinating work relied on disconnected tools.
- Finding suitable projects was hard. Talents had no single place to see what work was available and pick projects that fit their skills.
- Time tracking was fragmented. Tracking working time depended entirely on an external tool (TimeDocTer), separate from the work itself.
- Work was distributed through a WhatsApp group. When there was a new job, talents had to be contacted manually through a WA group — easy to miss, hard to track.
- Trello alone wasn't enough. Project coordination only ran on Trello, which saw little activity and left employees struggling to stay on top of their work.
03 · Goals
- Make it easy for employees to see what work is available.
- Make the salary received from each job clear and transparent.
04 · Research & Process
The design direction was shaped through discussions with the PM/stakeholders and with the users themselves, focusing on the day-to-day reality of how work was assigned, tracked, and paid before the product existed.
05 · Key Findings
The main insight from the research: instead of juggling separate tools, the answer was to combine TimeDocTer-style time tracking with a Trello-like work system into one app — so talents can discover available work, track their working time, and see their compensation in a single place.
06 · App screens
07 · Design system & components
The system is built from a small set of consistent building blocks — navigation, cards, tabs, filters, status/metrics, and form items — so any new screen reuses the same patterns instead of inventing new ones.
08 · Reflection
Working on Platon Talent strengthened my habit of designing systems, not just pixels. Because a mobile app has limited space, every component had to earn its place — and reusable patterns kept the product cohesive across many screens while still leaving room for personalized touches like the developer profile.
- Consistency — a shared component library so screens grow without diverging.
- Information hierarchy — the most important thing (the opportunity, the salary, the person) always leads.
- Handoff-ready — structured layers and clear naming so developers can implement confidently.
— Fegi Sucepto Priawan · UI/UX Designer