What Are Some Side Projects? A Honest Look at What People Actually Build
Photo by DS stories on Pexels

8 min read

From the studio

We build apps people actually keep.

Tinkrd is a small indie studio making focused, high-quality apps for everyday life. See what we're working on.

View our apps

Side projects are one of the most honest ways to learn something new, test an idea, or build something you actually want to exist. They range from tiny scripts that save you ten minutes a week to full products used by thousands of people. Here is a grounded look at what people actually build and how to think about picking one.

What are some side projects people commonly build?

Side projects fall into a handful of broad categories, and most successful ones sit clearly inside one of them. Knowing the category first helps you scope the work honestly before you write a single line of code.

Tools and utilities

Small tools solve a specific, repeatable pain. A browser extension that strips tracking parameters from URLs. A script that resizes images before upload. A CLI tool that formats your team’s commit messages. These projects are popular because the scope is small and the feedback loop is fast. You can ship a working version in a weekend and know within a week whether it is useful.

Content and media projects

Newsletters, podcasts, YouTube channels, and written courses all count as side projects. They take consistent time rather than bursts of coding, and they compound slowly. A newsletter about a niche topic can become a genuine business or a launchpad for a paid product later. The trade-off is that the feedback is slow and the work never really ends.

Apps for a specific audience

Mobile and web apps built for a narrow audience tend to work better than broad ones. Narrow means the user is easy to find, easy to talk to, and easy to market to. A budgeting app for freelance illustrators. A habit tracker for people in physical therapy. A story app that makes teeth brushing easier for kids. That last one is what we at Tinkrd shipped as Stepping Stones, and the narrow focus was the reason we could actually finish it as a two-person team.

APIs and developer tools

If you work in software, building something other developers use is a natural fit. An open-source library, a wrapper around a messy API, a self-hosted analytics tool. Developer tools spread by word of mouth inside communities like GitHub and Hacker News, which lowers the marketing cost. The downside is that developer users are also your harshest critics, which is mostly a good thing.

Games and creative experiments

Browser games, interactive fiction, generative art tools, and game jam entries are all legitimate side projects. They rarely make money, but they build skills and portfolios fast. Many developers who later shipped commercial products started with a game jam project just to practice shipping something complete.

How to pick a side project that you will actually finish

The biggest risk with any side project is not picking the wrong idea. It is starting one you will abandon after two weeks. A few honest filters help here.

For a deeper look at this filtering process, the guide on what makes a good side project covers validation and idea selection in detail.

Common side project stacks and what they cost to run

Keeping costs low matters when you have no revenue yet. Most early side projects can run for close to nothing. Here is a realistic look at what typical stacks cost per month at small scale.

Stack / Platform Monthly cost (small scale) Best for
Next.js on Vercel (hobby) $0 Web apps, marketing sites
Supabase (free tier) $0 Auth, database, storage
Railway (starter) ~$5 Backend services, cron jobs
Fly.io (small VM) ~$3 to $7 Dockerized apps, APIs
Apple Developer Program $99/year iOS / macOS app distribution
Ghost (self-hosted) ~$6 (VPS) Newsletters, content sites

A realistic first-year budget for a web app side project is under $200 if you use free tiers carefully. iOS apps cost more because of the developer program fee, but that is a fixed annual cost, not a per-user one.

A minimal side project setup that actually works

Most side projects die from over-engineering before launch. A working pattern for a simple web tool or SaaS looks like this.

# Minimal stack for a side project
# Frontend: Next.js (App Router)
# Backend: Supabase (auth + database)
# Hosting: Vercel
# Payments: Stripe Checkout (add only when you have users)

npx create-next-app@latest my-side-project
cd my-side-project
npm install @supabase/supabase-js

Start without a payments layer. Add Stripe only after someone has asked to pay you. This sounds obvious but most people build the billing flow before they have a single user. That is weeks of work solving a problem you do not have yet.

If you are thinking about a mobile app, the indie app development journey from idea to launch covers the full arc honestly, including the parts that take longer than expected.

Side projects that are worth building versus ones that waste your time

Not every side project is worth starting. Some patterns reliably lead nowhere.

Worth building: Projects where you are the target user, so you can test your own work. Projects that solve one specific problem completely. Projects where you can reach your first ten users without a marketing budget, through a community, a subreddit, or personal outreach.

Likely to stall: Projects that require a large network effect before they are useful, like a social network or marketplace. Projects that compete directly with a free feature inside a platform people already use. Projects where the first version requires six months of work before anyone can try it.

The honest truth is that most side projects do not make money, and that is fine. Many of the best ones exist to teach you something, build a portfolio piece, or just scratch an itch. Defining what success means before you start saves a lot of frustration later. For more on the full picture of what a side project actually is, this breakdown of what side project means is a good starting point.

Frequently asked questions

What are some side projects for beginner programmers?

Beginner-friendly side projects include a personal portfolio site, a weather app using a public API, a to-do list with local storage, or a simple web scraper. These are useful because they cover real skills like HTTP requests, state management, and basic UI without requiring a backend or payments layer. Pick one that solves something you actually care about so you stay motivated past the first week.

Can a side project turn into a real business?

Yes, many real businesses started as side projects, including GitHub, Craigslist, and Basecamp. The pattern is usually the same: a small tool built for personal use, shared publicly, and then iterated on based on real user feedback. The key is that the project needs to solve a problem people will pay to have solved, which is not guaranteed, so validate before you build the billing system.

How much time should I spend on a side project per week?

Most side projects that actually ship get four to ten focused hours per week. Consistency matters more than total hours. Two focused hours on a weekday morning five days a week beats a single twelve-hour weekend sprint followed by two weeks of nothing. Protect a regular time block and treat it like a meeting you cannot cancel.

Should I make my side project open source?

Open source makes sense if the project is a tool other developers would use, if you want community contributions, or if you want portfolio visibility. It is less useful for consumer apps or products where the code is not the differentiator. You can always open source a project later, but you cannot un-open-source it, so start closed if you are unsure.

How do I find ideas for side projects?

The most reliable source of ideas is your own repeated frustrations. Write down every time you do something manually that feels like it should be automated, or every time you pay for a tool that barely fits your use case. Also look at app store reviews for existing tools, because negative reviews are a direct list of unmet needs. For a structured approach to finding and filtering ideas, the guide on finding and validating app ideas walks through the process step by step.

Side projects are just the act of building something outside your main job or main commitment. The best ones start small, solve something real, and ship fast enough that you learn before you run out of motivation. Start with the smallest version you can honestly call useful, put it in front of real people, and go from there.

We’re building in the open

Tinkrd is a small studio making thoughtful apps for families. Our first app is launching soon.

See what we’re building

T
The Tinkrd Team

We are a small independent app studio in California. We write about what we are learning as we build and ship products, from first commit to first customer.