Weekend project ideas for developers: 13 you can ship by Sunday night

By Post your build ideas · 28 October 2026 · 10 min read

A weekend project is one that ends with a public URL or an installable file by Sunday night, built in roughly fifteen to twenty hours. The scope rule is one user, one input, one output, no accounts. The thirteen ideas below each come with a Friday evening, Saturday and Sunday plan, plus the feature to cut first when time runs short.

What actually fits in a weekend?

Count your hours honestly. Friday evening gives two or three, Saturday five to eight, Sunday four to six. That is about fifteen hours of real work, and some of it goes to setup, deploys and the bug you did not expect. So the design target is eight to ten hours of building, with the rest as slack.

A project fits when it has these properties:

One input and one output. A pasted expression becomes a sentence. A photo becomes a palette. If you need two screens to explain it, it is bigger than a weekend.
No accounts, no payments, no admin. Each of these costs half a day by itself. Add them in week two if anyone asks.
Data you already have or can generate. Waiting on an API key approval or a dataset takes you out of the weekend.
A deploy target you have used before. Learning a new host on a deadline is the most common way weekends slip.

If you can describe the finished thing in two sentences, it probably fits. If you want a wider list without the timebox, see side project ideas.

How should you split the weekend?

A default plan for fifteen working hours
Block	Hours	Goal	Done means
Friday evening	2–3	Spec, repo, deploy of an empty page	A blank page is live at a real URL
Saturday morning	3–4	The core transformation, ugly but working	The one input produces the one output
Saturday afternoon	2–4	Edge cases and the three failure messages	Bad input shows a clear message, not a crash
Sunday morning	2–3	Layout, copy, a share link or copy button	A stranger could use it without help
Sunday afternoon	1–2	Publish and ask five people to try it	A post is live and you are watching for replies

Deploy an empty page on Friday. A project that has never been deployed is a project that does not exist, and discovering a build error at 9pm on Sunday ends weekends. If you use an AI coding agent, write the spec on Friday and let it run through Saturday; how to build an app with an AI coding agent explains the loop, and Claude Code project ideas lists projects that suit it.

Which weekend projects are worth building?

Ordered from the safest scope to the most ambitious. Each entry gives the plan in three blocks and the one thing to cut first.

01 Cron expression explainer

A page where you paste a cron expression and read it as a plain sentence with the next five run times.

Friday evening: Spec the five-field grammar, deploy a page with a text box.
Saturday: Parse the fields, produce a sentence, compute next run times, write a table of 30 test expressions.
Sunday: Error messages for invalid input, copy button, a shareable URL with the expression in it.
Cut first: The reverse direction (English to cron).

The test table is what makes this safe. Thirty expressions with known sentences tell you in a second whether a change broke something. Shipped means a stranger pastes a weird expression and gets a correct sentence. The original board post is the cron explainer idea.

Read “Cron expression explainer” on the board and copy its build prompt →

02 Meeting cost ticker

A page that shows what a meeting is costing as the seconds pass, from headcount and a blended hourly rate.

Friday evening: Layout sketch, deploy, two number inputs.
Saturday: Timer logic that survives a background tab, currency formatting, start and pause.
Sunday: Full-screen mode for projecting in a meeting, a share link with the inputs preset.
Cut first: Per-attendee rates.

Timers in browser tabs drift when the tab is hidden, so compute cost from the start timestamp, not from a counter. That is the one real technical detail. See the idea on the board.

Read “Meeting cost ticker” on the board and copy its build prompt →

03 Palette from a photo with contrast checked

Upload a photo, get a five-color palette, and see which pairs pass the 4.5:1 text contrast threshold.

Friday evening: Spec the output, deploy an upload form that shows the image.
Saturday: Color extraction on a canvas, contrast ratio math, a grid of pass/fail pairs.
Sunday: Copy hex values, export as CSS variables, handle huge images by downscaling.
Cut first: Saving palettes to an account.

Everything can run in the browser, which means no server, no storage and no privacy page. The contrast formula is fixed by the accessibility guidelines, so half the project has a right answer. See the palette idea.

Read “Palette from a photo with contrast checked” on the board and copy its build prompt →

04 A group poll that closes itself

A shareable poll with a deadline that locks the vote and posts the result to everyone.

Friday evening: Data model: poll, options, votes. Deploy with a database.
Saturday: Create a poll, vote once per device, show live counts.
Sunday: Deadline logic, the closed state, a result page worth screenshotting.
Cut first: Notifications. Let the result page be the notification.

Compute “closed” from the deadline at read time instead of running a job that flips a flag. It removes a moving part and a class of bugs. Vote-once-per-device without accounts is a soft guarantee; say so on the page. The board has the poll idea.

Read “A group poll that closes itself” on the board and copy its build prompt →

05 RSVP that tells you who is actually coming

An invite link where guests answer yes, no or maybe, and are asked once more the day before.

Friday evening: Event page and a guest reply form.
Saturday: Replies list for the host, a private host link, a change-your-answer link.
Sunday: The day-before confirm, sent as a plain email, and the final headcount.
Cut first: Plus-ones and dietary fields.

Email is the risky part: deliverability takes time to get right, so test with your own address first and keep the volume small. Read the RSVP idea as posted.

Read “RSVP that tells you who is actually coming” on the board and copy its build prompt →

06 Can I leave the airport during this layover?

Enter an airport pair and layover length; get a plain yes, no or tight, with the reasons.

Friday evening: Choose ten airports, write the rules you will check.
Saturday: Rules engine: transit time, security, visa note, buffer. Output with reasons.
Sunday: A readable result card and a disclaimer that visa rules change.
Cut first: More than ten airports. Quality beats coverage.

Content is the hard part, not code. Ten airports you researched properly beat a hundred you guessed. State the date you last checked the data on the page. The idea exists on the board in two forms: the main post and a planner variant.

Read “Can I leave the airport during this layover?” on the board and copy its build prompt →

07 Typing test that sounds like a mechanical keyboard

A typing test with keystroke sounds and feel that mimic a mechanical keyboard.

Friday evening: Word list, text display, deploy.
Saturday: Input handling, words per minute, accuracy, one sound set.
Sunday: Sound options, a result screen, volume control, mute by default.
Cut first: Leaderboards.

Audio in browsers needs a user gesture before it plays, so start sound on the first keypress. Latency decides whether it feels right; test on a cheap laptop, not only your own. The typing test idea.

Read “Typing test that sounds like a mechanical keyboard” on the board and copy its build prompt →

08 Pickup game organiser

A link for a casual football game that fills places, tracks who is in, and tells you when you have enough players.

Friday evening: Game page with a place, a time and a player cap.
Saturday: Join and leave with a name, a waiting list, live count.
Sunday: Game full state, a reminder text to copy into a group chat, share card.
Cut first: Player ratings and team balancing.

The waiting list is the useful logic: when someone drops out, the first person waiting moves in. Test it with a table of join and leave sequences. See the board idea.

Read “Pickup game organiser” on the board and copy its build prompt →

09 Shared feeding log for pets

A log everyone in a household taps when the pet is fed, so it is never fed twice or not at all.

Friday evening: One shared log URL per pet, no sign-up.
Saturday: A big button, timestamp, who fed, last-fed banner.
Sunday: Install-to-home-screen support, a per-day view, undo for a mistaken tap.
Cut first: Medication tracking.

A link is the access control, so make it unguessable and say so plainly. This is a good weekend project because the whole thing is one button and one list. The original is shared feeding log for pets with several owners.

Read “Shared feeding log for pets” on the board and copy its build prompt →

10 Was this actually on sale?

Paste a product link and see its price history, to tell whether a discount is real.

Friday evening: Choose one store and check you may read its pages.
Saturday: Fetch the price, store it daily, show the line.
Sunday: A verdict sentence and the “first seen” date.
Cut first: Every store but one.

A real problem on day one: you have no history. Seed it with a promise (“tracking starts now”) and an honest empty state. Check each store’s terms before you fetch its pages. The board idea describes the use case.

Read “Was this actually on sale?” on the board and copy its build prompt →

11 Kids chore board with pocket money

A shared board where kids tick off chores and the balance of pocket money updates.

Friday evening: Chores list and a child profile with no real names stored.
Saturday: Tick a chore, add a payout, running balance.
Sunday: Weekly reset, a parent approval step, a simple history.
Cut first: Real money transfers. Track a balance only.

Children’s data deserves care: collect as little as you can, use first names or nicknames chosen by the parent, and keep it off public pages. The chore board idea is on the board.

Read “Kids chore board with pocket money” on the board and copy its build prompt →

12 Photo-to-dinner suggestion

Upload a photo of your fridge and get three dinner ideas from what the model can see.

Friday evening: Pick a model provider, test five fridge photos by hand.
Saturday: Upload, prompt, parse three dishes into a list.
Sunday: A “not what I have” button, rate limits, cost cap.
Cut first: Recipe steps. Return names and a short method only.

The cost cap is the part people forget: set a daily limit before you share the link, or one popular post becomes a bill. Ideas with photo input also have a version where the model misreads items, so show what it thought it saw. See fridge photo to three dinners.

Read “Photo-to-dinner suggestion” on the board and copy its build prompt →

13 Subscription graveyard from a bank CSV

Upload a bank statement export in the browser and list charges that repeat monthly.

Friday evening: Collect two sample CSV formats and write the matching rule.
Saturday: Parse, normalize merchant names, detect monthly repeats.
Sunday: Totals per year, a sorted list, a clear “nothing leaves your browser” note.
Cut first: Support for more than two banks.

This is the most ambitious of the thirteen because merchant strings are messy. If Saturday ends and detection is poor, ship a manual tick-box version and iterate. The original idea is on the board.

Read “Subscription graveyard from a bank CSV” on the board and copy its build prompt →

How was this list chosen?

By editorial judgment: one input, one output, no accounts, and a core that can be tested without a person in the loop. The hour plans are estimates of a reasonable split, not measured times, and your pace will differ. Every entry that links to the board is an idea a visitor posted; we picked the ones whose scope fits a weekend.

What do you cut when the weekend goes wrong?

Decide the cut order on Friday, while you are calm. A good order is: polish, then secondary features, then the second input type, then error handling for rare cases. Never cut the deploy or the core transformation.

A one-page weekend spec

Project: 
User: one sentence on who uses it
Input: 
Output: 
Shipped means: a stranger can do X without help
Not this weekend: (list at least three)
Cut order if late: 1) 2) 3)
Test: 10 example inputs with expected outputs
Deploy target:

That spec doubles as the prompt for a coding agent. The MVP scope planner and vibe coding project picker help you cut and choose, and how to scope an MVP explains the logic.

What counts as shipped?

A public URL or download that works on a device you do not own.
A sentence on the page saying what it does and what it does not.
One place you posted it, with a way to count replies.
A note to yourself: what you would build next if three people asked.

Then wait a week before adding anything. Whether anyone returned is the answer to “was this worth another weekend.” If you finish early or want more, browse ideas on the board or post an idea you won’t build so another developer can take it.

Frequently asked questions

What is a good weekend project for a developer?

One with a single input and a single output, no accounts or payments, and a core you can test with a table of examples. Small utilities, converters, calculators and one-button trackers fit. If you need two screens to explain it or an approval from a third party, it will not fit.

How many hours is a weekend project?

Plan for about fifteen hours of real work, split into two or three on Friday evening, five to eight on Saturday and four to six on Sunday. Aim to use eight to ten of them on building so setup problems and surprises have somewhere to go.

Should I use an AI coding agent for a weekend project?

It suits weekend projects well when the spec is one page and the output is testable. Write the spec and the example tests on Friday, let the agent build on Saturday, and spend Sunday reviewing and polishing. It saves time only if you can tell whether the result is correct.

How do I finish a weekend project instead of abandoning it?

Deploy an empty page on Friday, define what shipped means before you start, and write your cut order in advance. Projects stall when scope grows quietly. Posting the finished version publicly by Sunday night, however rough, turns it from a repo into something other people can react to.

Where can I find weekend project ideas?

Browse the Post your build ideas board, where people post ideas they will never build, across 31 categories. Each idea page has a generated build prompt for your coding tool, and a place to link what you shipped (links are not verified). Posting an idea needs no account.

Created with AI assistance and edited for this site. Examples are illustrative and do not represent customer research. About the publisher.