Release preparation

NozzleNote is not publicly available yet.

NozzleNote by BMR is still in development. This page explains the planned release path for the first public desktop Core and keeps expectations conservative until real release files, notes, support scope, and reviewed legal text are ready.

No public files yet

No installer, binary, checksum, checkout, signup form, or release date is published here. This page is a readiness checklist for future release preparation, not an active download flow.

No public download yet

This is a release-preparation placeholder, not a file download page. The first public release is planned to focus on the free desktop Core: printer profiles, maintenance tasks, history, parts, incidents, and local backup. Those plans remain in development and do not mean files are ready today.

Real download links should be added only after packaging, versioning, documentation, known limitations, backup guidance, support boundaries, manufacturer-independence language, and draft legal placeholders are reviewed.

Planned release checklist

What should be ready before files are published?

These items keep the release message practical, beginner-friendly, and cautious. They do not announce a launch date or provide download files.

Planned

Windows build

The first public package is planned to start with a clearly labeled Windows desktop build after packaging work is ready.

Required

Version number

Any future release should include a visible version number so documentation, known limitations, and support notes can refer to the same build.

Planned

Installer or portable package

The package format is not final yet. A future release should explain whether users receive an installer, a portable package, or both.

Required

Release notes

Release notes should describe included Core workflows, what remains planned, and what is not available yet.

Required

Known limitations

Known limitations should be listed before files are published, including unsupported workflows, roadmap-only ideas, and model coverage boundaries.

Required

Backup guidance

Local-first users should receive clear guidance for manual backups, restore expectations, and data-location notes before public files are posted.

Required

Support scope

Support notes should clarify which app questions may be covered and which printer service, warranty, safety, or manufacturer issues remain outside scope.

Required

Manufacturer disclaimer

Release copy must state that NozzleNote by BMR is independent and not affiliated with, endorsed by, sponsored by, or officially connected to manufacturers.

Required

Privacy notice

Privacy language should be reviewed before any account, licensing, diagnostic, support intake, cloud, mobile, analytics, or payment workflow launches.

Required

Terms and license placeholders reviewed

Draft terms, license, refund, and disclaimer pages should be reviewed before public distribution or any commercial flow is introduced.

What to expect before download

  • NozzleNote is not publicly available yet.
  • No real download links, installers, binaries, checksums, purchase links, signup forms, or release dates are available from this page.
  • The first public release is planned to focus on the free desktop Core: printer profiles, maintenance tasks, history, parts, incidents, and local backup.
  • Optional paid verified catalogs and early supporter funding are future roadmap directions and are not part of a public checkout flow on this website.
  • The app is intended for maintenance records and planning, not direct printer control, manufacturer service, or machine-driven diagnosis.

Safety and data note

NozzleNote by BMR is planned as a local-first desktop maintenance tracker. Users should keep their own backups, follow printer manuals and safety guidance, and treat maintenance reminders as helpful planning prompts rather than assurances, official service instructions, or machine-made fault findings.

Preliminary legal pages have been added for planning and future review. They are draft placeholders only and do not announce public availability, paid plans, final license terms, refund terms, or legal compliance.