Zuber
Amin

Building a résumé usually means fighting someone else's Word template, or handing your data to a web tool that locks you into one layout. On a phone, that gets worse — most builders reduce you to a single generic design because supporting real variety is hard. I wanted neither: your content, and real design freedom, on the device already in your hand.

The hard part was never "make it look nice." It was: how do you support fifty genuinely different visual identities — different layouts, sidebars, skill-bar styles, photo shapes, fonts — without writing fifty near-duplicate screens that all drift out of sync the moment one of them needs a fix?

I modeled a template as pure data, completely separate from the person's content. A CVTemplate is a description — colors, heading and body fonts, a layout enum, a skill-visualization style, a photo-frame shape, a pattern — with nothing about any individual's résumé inside it. The person's data lives in its own CVModel. Any template can render any person's content, because neither one knows the other exists.

Three problems fell out of that decision, and each needed its own answer:

• Fifty visual identities, one codebase. Layout, skill-style, pattern, and photo-frame are each their own enum. A single skill-visualizer widget reads a template's style enum and switches between real, distinct implementations — a segmented circular arc for one template, a DNA helix for another, a thermometer fill for a third — each its own composition, not a reskinned variant of the others.
• Letting people customize without breaking the designer's intent. Font size, icon color, header color, and photo-frame shape are all separately overridable — but every override defaults to null, meaning "respect the template." A sentinel-object pattern in copyWith lets the app tell "the user didn't touch this" apart from "the user explicitly cleared it," and a set of small resolver methods (resolveFont, resolveHeaderColor…) decide, field by field, whether the template or the user wins.
• One job title, two different vocabularies. The career picker offers sixty-eight specific titles ("Chemical Engineer"); the auto-fill summaries are written against fifteen broad categories ("Engineering"). I bridged them with an explicit lookup map for the direct cases, and a fuzzy keyword-matching fallback for anything typed in freehand that doesn't have one.

Underneath all of it, each résumé is saved into its own local storage "slot" with a lightweight index, so switching between several drafts doesn't mean re-parsing every saved résumé just to show a list — and any résumé saved under the app's older single-slot format migrates into the new structure automatically the first time it loads, without losing content.

One data model, fifty independent visual identities, and zero per-template content duplication. Add a fifty-first template and it's a new data description — no new form, no new save logic, no touching the other forty-nine.