OpenHome / Product & developer experience
← All priorities
Priority 03

Make onboarding reproducible and preserve developer work

Missing assets and conflicting guidance interrupt setup; an inspected migration path puts unpushed work at risk.

Recommended next move

Ship one tested onboarding path and protect local work before migration.

What I observed

The reviewed onboarding materials and artifacts had missing starter assets, unavailable example links, conflicting authentication instructions, and differences between local validation and hosted upload acceptance. Source inspection also identified a migration path that could discard unpushed work; I did not execute that destructive path.

Why it matters

A developer can follow the instructions correctly and still fail before reaching a first result. Migration can put existing work at risk. Documentation alone cannot repair assets missing from the package itself.

Recommended behavior

Provide one clearly identified, versioned onboarding path that includes its starter files, specifies the correct credentials and uses validation rules consistent with the hosted service. Detect modified and untracked work before migration; stop safely or create a verified recoverable backup.

Acceptance

A fresh evaluator reaches a first correct Ability result using only the published steps and packaged files. Record time and undocumented interventions rather than inventing a performance target. Referenced examples resolve at the tested version. Local and hosted validation agree on representative accepted and rejected code. Migration tests preserve modified, untracked and unpushed work.

Evidence limits: findings apply to the reviewed source, packages and documentation snapshots; current replacement releases should be retested. No actual loss of customer work was demonstrated. Evidence references: D01, D03, D04, D06, D07, D17.