Skip to content

Latest commit

 

History

History
35 lines (26 loc) · 1.93 KB

pake-grade-goal.md

File metadata and controls

35 lines (26 loc) · 1.93 KB

Pake-grade goal

This is the product bar for making appbun feel worthy of a larger open-source community.

North star

Make URL -> desktop app feel instant, inspectable, and reliable enough that people share the command before they explain the tool.

Current focus

  • One-line creation for recognizable apps through built-in recipes.
  • Concept-based discovery so people can move from an intent like design or music to a useful app recipe.
  • A doctor command that helps users and contributors diagnose local setup issues before filing bugs.
  • Cross-platform packaging scripts that make native-runner builds obvious without pretending to cross-compile locally.
  • Generated GitHub Actions release workflows that turn native-runner guidance into uploadable artifacts.
  • Generated Electrobun projects that are normal codebases, not opaque wrappers.

Product principles

  • The first command should be memorable.
  • The generated project should be editable by a real developer.
  • Common packaging failures should produce actionable diagnostics.
  • Platform builds should be honest about native-runner requirements.
  • Release automation should be present by default, but remain inspectable and easy to edit.
  • Community contributions should have obvious entry points: recipes, docs, shell polish, packaging, and screenshots.
  • Recipes should form a small, useful concept map rather than a flat pile of links.

Near-term milestones

  • Expand recipes carefully with stable, recognizable targets.
  • Use concept metadata to make related app categories obvious without adding a heavy registry.
  • Add richer generated-app controls where Electrobun support is stable: reload, external-open behavior, and app metadata.
  • Improve Windows and Linux packaging paths after macOS remains boringly reliable.
  • Keep cross-platform build scripts aligned with Electrobun's native-runner guidance.
  • Keep showcase screenshots current enough for README visitors to trust the project.