Contract Android OS Experience Design Engineer (Launcher + System UI Design System)

About the role

We’re building a new Android-based OS experience for a first-generation smartphone. The goal is a slick, premium, fast interface with a cohesive visual identity and a highly polished “system-level” feel across the home screen, app drawer, search, and assistant-style surfaces.

We need a Contract Android OS Experience Design Engineer to create a production-ready design system + UI pack that engineers can implement with minimal ambiguity. This is a hands-on role combining product design craft with implementation awareness (Android constraints, motion feasibility, asset formats, handoff discipline).

This is not “just pretty screens.” We need a structured pack: tokens, components, screens, iconography, motion specs, exports, and handoff docs.

Contract type

• Contract / Freelance
• Duration: 2–6 weeks (scope-dependent)
• Location: Remote (West Africa time zone overlap preferred, but not required)
• Start: ASAP

What you will own (core deliverables)1) OS Design System (Tokenized, production-ready)

Define and deliver a cohesive design system including:

• Color tokens: brand palette + semantic tokens (primary, secondary, surface, background, error, success, warning, outline, elevation)
• Light/Dark themes: full token sets with accessibility/contrast checks
• Typography scale: font family selection + sizes + weights + line heights + letter spacing
• Spacing system: 4/8dp grid rules, layout margins, component padding standards
• Corner radius + elevation/shadows: standard radii and elevation guidelines
• Interaction states: pressed/focus/disabled/loading states
• Accessibility guidance: tap targets, font scaling, contrast recommendations

Output requirements

• Figma tokens clearly labeled and structured
• Optional token export (JSON) if using a token plugin

2) Launcher UI (Home + App Drawer + Search)

Create a complete UI/UX spec for:

• Home screen
• wallpaper behavior, widget placement, dock style
• folders (visual treatment + open/close behavior)
• long-press actions
• App drawer
• layout, search, sorting/filter patterns (if any)
• empty state, loading state, “no results”
• Global search
• suggestions, recent actions, result types (apps/settings/contacts)
• Edit mode
• icon rearrange, add widget, change wallpaper, theme selection
• Quick actions
• contextual actions from app icons (shortcuts)

Must include

• Visual specs + spacing + states
• Key flows (user journeys) in Figma
• Engineer-facing annotations (what’s static vs dynamic)

3) Assistant-Style Surface (Left Swipe Panel / Feed)

Design a system-level feed/panel surface that feels native:

• Daily brief card (calendar/tasks)
• Summaries (messages/calendar highlights)
• Quick actions (reminders, notes, call, navigation, utilities)
• Voice entry + text entry
• Loading/empty/error states

Must include

• Content layout rules
• Card system rules (spacing, elevation, radius)
• Interaction behaviors per card type

4) Visual Identity Assets (Icons, Wallpapers, UI Graphics)

Deliver:

• App icon system
• OS app icon + key system app icons style
• Adaptive icon style rules (foreground/background layers)
• System icons set
• minimum 30–50 icons for v1 (settings, toggles, quick actions)
• Wallpapers
• 5–10 premium wallpapers
• Optional subtle graphic motifs/patterns used across the OS

File outputs

• Icons: SVG source + export-ready assets
• Wallpapers: WebP (preferred) + PNG if needed
• App icons: adaptive-ready files + guidelines

5) Motion & Transitions Spec (Premium “Feel”)

Define motion language that makes the OS feel fast and expensive:

• Motion principles (snappy vs smooth vs elastic)
• Durations (ms) for core transitions
• Easing curves recommendations
• Motion staging (delays, stagger rules)
• Key transitions storyboarded:
• app open/close
• home ↔ app drawer
• panel slide
• card expand/collapse
• folder open/close
• search open/close

Deliverables

• Motion spec sheet (Figma + short written doc)
• Optional Lottie JSON for specific in-app animations (only where appropriate)

6) Engineering Handoff Package

Provide clean handoff so implementation is fast:

• A short Handoff Doc (PDF/Notion/Google Doc) covering:
• token reference
• component behaviors
• do/don’t rules
• states and edge cases
• Export folder containing:
• wallpapers
• icons (SVG + exports)
• font files (with license note)

Required skills & experience

• 3+ years in Product Design / UI/UX (mobile)
• Strong experience building design systems (tokens + components + patterns)
• Strong visual craft: typography, spacing, hierarchy, polish
• Comfort designing for Android constraints (status bar, navigation patterns, touch targets)
• Proficiency in Figma (components, variants, auto-layout, libraries)
• Strong iconography skills (grid, strokes, optical alignment)
• Solid motion fundamentals for UI interactions

“Design Engineer” expectations (implementation-awareness)

You do not need to be a full software engineer, but you must:

• design with reusable components and token discipline (not one-off screens)
• understand what is expensive/hard on Android (heavy blur, complex shader effects, excessive unique UI)
• communicate behaviors precisely (states, transitions, edge cases)
• collaborate with engineers and iterate based on feasibility feedback

Bonus (nice to have)

• Familiarity with Material 3 concepts (without being constrained by them)
• Experience with launchers, system UI, or motion-heavy products
• Basic familiarity with Android resource formats (colors.xml, fonts, vector assets)

What success looks like

At the end of the contract:

• We have a complete, cohesive OS design system
• Engineers can implement launcher + assistant panel with minimal guessing
• UI works beautifully in light + dark mode
• Motion specs feel premium and are feasible to build
• Assets are delivered in correct formats, organized cleanly

Apply Here:

https://jobs.usejuno.io/clive-hardware-bgehu/jobs/69469e29e6b3123bb70138f3

<