Index of every page on this site: llms.txt
All skills
erkamyaman avatar

/native-vs-web

@7fcc555
Run it yourself

Use when deciding whether an app should be native, web, or hybrid (Ionic/Capacitor) now that agents make native code cheaper to produce.

  • 2 files
  • 2.6 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/erkamyaman/dhh-p-bloom-agent-skills/native-vs-web

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈38 tokens for metadata: the name and description. ≈453 when used: this file. ≈157 more on demand in 1 file.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈152 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Native vs web

Inspired by DHH's Rails World 2026 keynote: https://www.youtube.com/watch?v=vDjW_dRyKXY

From the talk

DHH says Hey is being rebuilt as native apps because agents have cut the cost of native development, and he cites Shopify's rewrite of its Shop app as native. He says the web remains best when users won't install anything, such as Basecamp's guests, and admits he doesn't have all the answers on where to draw the line. The decision table and steps below are our additions. Ionic and Capacitor are not discussed in the talk.

The talk argues that web apps were often chosen because small teams couldn't afford several native apps, and that agents are shrinking that cost. This skill helps you re-check the decision per app instead of assuming the old answer.

When to use

  • Starting a new app or a major rewrite.
  • An existing hybrid app has hit performance, fidelity or platform-feature limits.

Steps

  1. List what the app needs: offline, background work, push, sensors, widgets, system integration, startup speed.
  2. Ask who uses it: returning users who will install it, or one-time visitors who won't.
  3. Score each option (web, hybrid with Capacitor, fully native) against the list using references/decision-table.md.
  4. Estimate the maintenance cost honestly: number of platforms, number of people who can review the code.
  5. Prototype the riskiest screen in the leading option and measure it before committing.

Verification

Compare the prototype to the current app on startup time, scrolling smoothness and the platform features that matter. If the gain is small, stay with what you have.

Caveat

"Native is now nearly free" is a claim from the talk, not a measured fact. Agent-written native code still needs testing, store review and long-term maintenance.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 7fcc555. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 2 months ago

README badge

README badge for erkamyaman/dhh-p-bloom-agent-skills/native-vs-web