Ideas · Idea list · Developers

25 side project ideas
for developers who want to ship

The best side project ideas for developers are small enough to finish in a few weekends and personal enough to keep you going: a tool that fixes your own daily annoyance, a clone of a product to learn its hard part, an open-source library you wish existed, or a tiny paid tool for a niche. Pick your goal first, then scope one feature you can ship in two weeks.

By , FounderUpdated 6 min read

Share

Quick answer: What are good side project ideas for developers?

  1. Choose the goal — learn, portfolio, community or income.
  2. Scratch your own itch — you'll use it, so you'll finish it.
  3. Scope to two weekends — one core feature, shipped.
  4. Ship in public — a README, a demo link, a short post.
  5. Stop or continue deliberately — finished beats perfect.

Key takeaways

  • Unfinished side projects teach less than small finished ones.
  • Clones are great for learning if you focus on the one hard part of the original.
  • Open-source contributions build reputation faster than solo repos nobody sees.
  • If you want income, choose a niche that already pays and charge from day one.
  • Check your employment contract before building anything commercial.

Every developer has a graveyard of side projects: a repository with an ambitious README and three commits. The problem is rarely the idea. It's that the project had no clear purpose and no finish line. So this list is grouped by what you want the project to do for you — and ends with a method for actually shipping it.

What are good side project ideas for developers? At a glance: Choose the goal; Scratch your own itch; Scope to two weekends; Ship in public; Stop or continue deliberately.
At a glance: What are good side project ideas for developers?

First, pick the goal

Side project goals and finish lines
GoalChoose a project that…You're done when…
LearnForces you to use a new technology for its hard partYou can explain how it works
PortfolioShows end-to-end engineering with real usersIt's deployed, documented and used
CommunityHelps a group you belong toPeople use it without you prompting them
IncomeSolves a paid problem for a nicheSomeone pays

For yourself: scratch your own itch

1. A personal finance dashboard from bank statements

Parse statement PDFs and categorise spending. You'll learn parsing, data modelling and charts — and you'll actually use it.

2. A WhatsApp bot for your family

Birthdays, bill reminders, shared shopping lists. Teaches webhooks, messaging APIs and state.

3. A reading list with spaced reminders

Save articles; get them back when you're likely to forget. Teaches scheduling and email.

4. A home-network status page

Monitor your Wi-Fi, devices and internet speed on a Raspberry Pi. Teaches networking and dashboards.

5. A meal planner from your fridge

Photograph ingredients; get recipes. Teaches image recognition APIs and recommendation basics.

To learn: build-your-own

6. Build your own Redis

A key-value server speaking a simple protocol, with persistence. Teaches networking, concurrency and data structures.

7. Build your own Git

Objects, commits and branches from scratch. Teaches content-addressable storage and hashing.

8. A tiny interpreter

Lexer, parser and evaluator for a small language. Teaches how every language you use works.

9. A collaborative text editor

Real-time editing for two users. Teaches WebSockets and conflict resolution — the browser APIs are well documented on MDN4.

10. A URL shortener at scale

Then load-test it. Teaches caching, databases and performance measurement.

For your portfolio

11. A full-stack app with real users

Any small app — but with 50 real users and their feedback in the README. That evidence is rare and memorable.

12. A mobile app using the camera

Scan, recognise, act. Shows a phone-native skill set.

13. A data story from public data

Analyse an open dataset and publish an interactive article. Shows analysis and communication.

14. A design system and component library

Tokens, components, documentation and accessibility tests. Shows craft for front-end roles.

15. A CLI tool you use daily

Automate something in your workflow, then package and publish it.

For the community

16. Translations for an open-source project

Add Indian-language support to a tool you use. GitHub's guides help you find projects to contribute to2.

17. A missing library for an Indian API

A clean SDK for a public API that lacks one in your favourite language.

18. An accessibility audit tool

Scan pages for common issues and explain fixes plainly.

19. Tools for your local NGO

Volunteer scheduling, donor receipts or beneficiary records. Real users, real impact.

20. A tutorial site for a niche topic

Teach what you just learned. Writing it clarifies your own understanding.

To earn a little

21. A browser extension for a profession

Recruiters, salespeople, teachers — find a repetitive browser task and automate it.

22. Templates and starter kits

A polished starter for a stack, sold once.

23. A niche job board

Jobs for one skill in one region, monetised by posting fees.

24. An API wrapper as a service

Turn a messy public data source into a clean, paid API.

25. A paid newsletter tool for a community

A small tool that solves one job for creators in a niche you know.

How to actually finish

Diagram of 6 steps for how to actually finish: 1. Write the finish line; 2. Scope to one feature; 3. Work little and often; 4. Ship rough, in public; 5. Pick a licence; 6. Decide consciously.
How to actually finish
  1. Write the finish line in one sentence before you start.
  2. Scope to one feature you can ship in two weekends.
  3. Work little and often — 30 minutes daily beats a lost Saturday.
  4. Ship rough, in public — a demo link and README. Posting on Show HN has its own etiquette worth reading1.
  5. Pick a licence if it's open source3.
  6. Decide consciously after shipping: continue, pause or archive.

If a project starts earning, micro-SaaS ideas you can build solo shows how to grow it. For a 48-hour sprint, see hackathon project ideas.

Key terms, defined

Side project — work outside your main job, for learning, portfolio or income. Scope — what a project includes. Show HN — Hacker News posts sharing something you've made. Open-source licence — terms for how others can use your code.

Frequently asked questions

How do I choose a side project?

Decide what you want from it — learning a technology, a portfolio piece, helping a community, or income — then pick a problem you personally have. Personal use keeps motivation alive, and a clear goal tells you when you're done.

How do I finish a side project?

Scope ruthlessly to one core feature, set a two-week deadline, work in small daily sessions, ship a rough version publicly, and decide afterwards whether to continue. Publishing early creates accountability.

Can side projects make money?

Some do, usually as small tools for a niche, browser extensions, templates or micro-SaaS. Most earn little. Treat income as a bonus unless you deliberately target a paying niche and price from the start.

Do side projects help get a job?

Yes, when they show real engineering decisions: a deployed project with users, clean code, tests and a clear README tells interviewers more than certificates. Be ready to explain trade-offs you made.

Can I build side projects while employed?

Usually, but read your employment contract and company policy on outside work and intellectual property. Avoid using company time, equipment or confidential information, and ask HR if anything is unclear.

What tech stack should I use for a side project?

Use what helps your goal: a new stack if learning is the point, or the stack you know best if shipping is. Managed hosting and databases with free tiers keep costs and maintenance low.

Sources

  1. Hacker News — Show HN guidelines
  2. GitHub Docs — Finding ways to contribute to open source on GitHub
  3. Choose an open source license
  4. MDN Web Docs — Web APIs
  5. Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Test the idea

Find out if users want it before you build it.

A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.

Free certification

Turn what you know into a credential.

Free, test-based UX, UI and product certifications. Answer real product scenarios, graded on our server, and earn a founder-signed certificate anyone can verify and you can add to LinkedIn.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy