Configurable Wear OS Watchface Engine

I’m hiring a Wear OS developer to build a config-driven watch face system (not a single face). The goal is Facer-creator-like control so I can create many different faces without code changes.

Fixed total budget: $1,000. Work will be delivered in 6 milestones, starting with a $100 gatekeeper milestone to prove the architecture is truly config-driven (if Milestone 1 fails, the project stops).

Core requirements (included in fixed price — no add-ons)

Creator configurability (must not be hard-coded):

Config-driven X/Y positioning for every element

Config-driven sizing (text, icons/images, progress arcs)

Configurable layering / z-order

Config-driven opacity + conditional visibility rules (time/mode/data/sun-state)

Multiple layout templates (A/B/C) selectable via config

Assets & typography:

Import and assign custom fonts (TTF/OTF) per text element

Import images (PNG; SVG where supported by WFF) for backgrounds/icons/overlays/masks

Weather icon pack import + condition→icon mapping, including day/night variants

Data to display + tap interactions (included):

Media “Now Playing” (title/artist/state) + tap opens system media

Next calendar event + tap opens calendar/event

Weather: current + hourly (3–6h) + daily (3–5d) + precip % + tap opens weather

Sunrise/sunset (synced) + usable in rules + tap opens weather

Activity: steps, last HR, calories + tap opens health

Battery % + tap opens battery/system screen

Progress indicators (included):

Bars/arcs for steps, calories, battery

Configurable geometry (thickness/length/radius/sweep)

Must support tap zones where applicable

Theme interaction (included):

Tap-to-cycle predefined color themes (no custom color picker UI)

Theme selection must persist

Tap zones must not conflict with tap-to-open actions

Curved/arc text (included):

Configurable arc geometry (center/radius/start/sweep)

Must respect fixed sweep (no auto-expand)

Works with layering and rules (and tap if used)

Deliverables each milestone

Working APK + full source

Short documentation for config fields and how to create new layouts/faces

Code must remain reusable (no “one-off hard-coding”)

If you have experience with Wear OS watch faces (WFF) and building config-driven rendering/layout systems, please bid and briefly describe how you would implement the config-driven layout + layering + rules.