CV Spark: offline CV & resume maker

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 it 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 this: how do you support fifty genuinely different visual identities (layouts, sidebars, skill-bar styles, photo shapes, fonts) without writing fifty near-duplicate screens that drift out of sync the moment one of them needs a fix?

I modelled a template as pure data, completely separate from the person's content. A CVTemplate is a description: colours, heading and body fonts, a layout enum, a skill-visualisation style, a photo-frame shape, a pattern. It holds nothing about any individual's résumé.

The person's data lives in its own CVModel. Any template can render anyone's content, because neither one knows the other exists.

That decision raised three problems, and each needed its own answer.

Underneath, each résumé is saved in its own local storage slot with a lightweight index, so switching between drafts never re-parses every saved résumé. Résumés saved in the older single-slot format migrate into the new structure automatically on first load, without losing content.

String resolveFont(CVTemplate t) => fontFamilyOverride ?? t.headingFont;
Color  resolveHeaderColor(CVTemplate t) => headerColorOverride ?? t.primaryColor;

One data model, fifty independent visual identities, and zero per-template content duplication. Adding a fifty-first template means writing a new data description. No new form, no new save logic, no changes to the other forty-nine.