Any Full Stack Webapp Project Ideas?

I am almost done with the 100DaysOfCode challenge (in the 70s), but my main problem is I’ve ran out of project ideas to work on. The next one I wish to focus on is a full stack webapp, but I have nothing in mind. Most of the stuff I find are boring are overdone (e.g. to do list, etc).

Any ideas to suggest? I plan to use a MERN stack (Mongo, Express, React, Node). Maybe GraphQL if appropriate.


Also, I’m open to doing some GitHub code contribution if I find it appealing and have the experience needed (doesn’t have to be unique nor does it have to be full stack, but I have my own limits in free time too so… :slight_smile: )

Why don’t you make a blog?
Keystone.js it is very useful to get you going with basic expressJs settings and mongoose so you can save some time. From there your imagination is the limit.
I built my blog on top of KeystoneJs, but you can do anything really.
This is ME*N stack …You can have it as MERN, it is up to you.
Have a read here you may find it interesting.


Another Idea, create a database with all the bank and bank branches locations, with address, opening hours and phone numbers from your country. (those are public informations).

Then create a website which allow people to search by Name of Bank and branches or whatever criteria you want.
Then you can add a Leaflet Api (Leaflet is free and easy) or google maps api to display a map and you can get google api places to search by address and display.

This idea has potential to bring you huge revenue if you place strategically google addsense on your site.

The informations are free and everything is legal.
If you making this working and add to your portfolio, any employer will want you.

Mongodb/mongoose Schema on mlab for database, React-Redux Bootstrap,reactstrap for front-end, expressJs/NodeJs ecosystem for backend, Heroku for hosting. Amazon Route 53 and Amazon S3 Bucket for domain name and routing to heroku.

For quick start you can use CMS keystoneJs.


Good luck.


Nice suggestion :clap: :clap:

1 Like

I love that idea! Different from the usual project ideas. I’ve also always wanted to use the Google maps API in someway but never thought of an idea that would utilize it. Thank you!! :slight_smile:

Just to clarify, for the create a database part, do you mean I can use w/e methods (e.g. manually copy/paste, etc)?

Yes, I don’t thing you can find this type of information from any public api. If you can, obviously use it, but if you make your own database and is good enough don’t give it further for free :)) (maybe do your own api and sell it).
You don’t have to limit yourself to the bank idea, just find something you know people need to use so your site going to have organic visitors for the content.

1 Like

Got it. Thanks! I was a tiny bit skeptical since there is almost an Api for everything these days haha.

While that’s true, writing your own API demonstrates that you have the right backend chops for full stack. This is especially crucial when someone wants to see if you properly understands RESTful design and security implementation.

It is not as readily accessible as a flashy front-end, but the right people will appreciate a properly designed rest API, for example an interviewer.

1 Like

Yeah, I’ve made a few REST APIs before or REST backends before.

Hmm, do you by any chance have any hard project ideas to suggest? I’m not expecting something startup-worthy, just something harder lol. Much harder than a to do list and blog. Something one would consider as an “advanced” level project.

A somewhat popular system design prompt during my interview cycle was design a microblogging platform, in essence, twitter. When you answer it, it requires a lot of theorizing and thinking about complexity and scalability, but you can also simplify it into a basic full stack project.

It is a full-stack project you can do on your own, there are even tutorials for it, but sit down, figure out the system design on your own. Think about how you organize the system, what are your key entities, what core functionality should be implemented as an MVP.

To add complexity, break down one of your full-stack application backend into interacting microservices or even serverless. Practice Domain Driven Design and event-driven architecture, complexity builds up when your stack is not simply a vertical pipe, and real-world systems are rarely simple


Finance calculator with expenses, incomes and categories via tags, with totals and stuffs. Similar to a to do but with filtering, searching, highlighting duplicate records. All saved into db and made as spa.
I’m currently doing it in excel and thinking of making an app for PC (spa as a web app).