tiredof.app
For developers

Ship a Dashlet.
Reach people tired of stuff.

We host. We distribute. We handle the money. You ship one small tool that does its job. Same code powers iOS when we launch it.

80/20 revenue splitNo fees on free toolsiOS distribution
dashlets/screenshot-resizer/manifest.ts
// One file describes the tool.
export const manifest = {
  slug: "screenshot-resizer",
  title: "App Store Screenshot Resizer",
  tagline: "Drop a screenshot. Get every size Apple wants.",
  category: "app-store",
  keywords: ["screenshot", "ios", "ipad"],
  status: "live",
  pricing: { kind: "free" },
  author: "you",
} satisfies DashletManifest;
Distribution

Land in the catalog.

When someone types what your tool fixes, you show up. Hybrid fuzzy + LLM search means natural-language queries reach you.

Payments

Free or paid. We handle the money.

Stripe is wired in. Set your own price or ship free. We take 20% on paid Dashlets, you keep 80. No fees on free tools.

Cross-platform

iOS comes for free.

Manifests are portable JSON. The same Dashlet ships on iOS the moment we launch the app, with no extra work from you.

How it works

Two files. One Dashlet.

A Dashlet is a manifest plus an implementation. The manifest describes the tool. The implementation builds it. That's it.

01

Write the manifest

A small TypeScript object: slug, title, tagline, category, keywords, pricing, status. Validated by Zod at build time.

02

Write the React component

One default-exported React component. Use any client-side libraries: Canvas, WebAssembly, fetch. Most tools never touch a server.

03

We publish it

Once approved, your Dashlet is live at tiredof.app/dashlet/your-slug, and at /by/your-handle as part of your portfolio.

We handle
  • ·Hosting + global CDN
  • ·Stripe payments + subscriptions
  • ·User accounts + sessions
  • ·Search + discovery in the catalog
  • ·Your developer profile + verified badge
  • ·iOS distribution when the app launches
  • ·Support inbox + abuse reports
You handle
  • ·Building one tool well

That's the deal. We took the parts that suck so you don't have to.

Revenue

You keep 80%.
We keep 20%.

No platform fees on free Dashlets. Paid Dashlets share revenue 80/20. Monthly payouts to your bank, no minimum, no surprise deductions.

On a $5/mo Dashlet
You$4.00
Tiredof$1.00
Monthly payouts to your bank. Free Dashlets: no fees, ever.
Get in early

Self-serve isn't open yet.
Get in line.

The dev portal is being built. Join the list and we'll let you in as soon as publishing flows are real. Tell us what you'd build. It shapes what we ship first.

FAQ

Questions you might have.

When does the dev portal open?+
We're building it. Waitlist members get the first invites. No firm date; we'd rather ship it right than ship it soon.
What stack do I need to know?+
The manifest is a TypeScript object validated by Zod. The implementation is a React component. We use Tailwind v4 and Geist for shared design. You can use them or bring your own styles.
Who owns the Dashlet code?+
You do. We license what we need to host and distribute it. Pull your Dashlet anytime; we'll deactivate the listing.
Can I use server-side code?+
Most Dashlets run entirely client-side. That's what makes them fast. For tools that genuinely need a server (OCR, video transcoding), we'll provide hosted endpoints once the portal opens.
What about my own users / analytics?+
You get aggregate usage stats per Dashlet (visits, clicks, conversions). We don't sell user data, and neither can you. That's in the publisher agreement.
Is there a quality bar?+
Yes. We approve every Dashlet before it goes live. The bar is “does it actually do the thing it says?”, not a beauty contest.

Build the thing you keep wishing existed.

We'll bring the audience.