Just Make Something

Fill out a form of what you want to build. Get your custom product stack. Answer a few questions to get your custom no code stack of tools and turn your idea into a reality.




Send me my stack!


Side Project Stack - Get the best tech stack to make your next Indie Maker App | Product Hunt Embed

Save Time Making Your No Code App


Side Project Stack works by sourcing hundreds of stack possibilities from projects within our list, to create your very best approach. Over 100+ combinations in the app builder sources and narrows down to the single best stack for your custom project. Getting started is easy. Answer a few questions. Get your custom stack.


🔍


Front End: Typeform, Table2Site Front End Notes: Typeform is used to gather product ideas and submit them from the main #requestforproduct landing page. "Table2site gives the ability to build elegant sites with cards, lists and filters. The best use of the platform is when you curate useful, meaningful content. You can tweak the design of the platform. The more creative the better the product is." - Sharath

Back End: Airtable Back End Notes: "Airtable acted as a CMS where I mapped the content to key-value pair which reflects on the front end visual template." - Sharath

Front End Output: Table2Site>Twitter Front End Output Notes: "Users can then explore the idea in detail from comments, links, etc." - Sharath

Front End: Coda Front End Notes: Coda is used for the online quiz and the form for email submission from the user.

Back End: Coda

Front End Output: Email Front End Output Notes: Users can input their email to be sent an email with their results.

Front End: Remetea: carrd.co Back End: Remetea - Coda Back End Notes: Used coda for the logic around recommending different variations of tea depending on the user preference.

Front End Output: Remetea - coda Front End Output Notes: Remetea, can get results within code application.

Front End: JQuery, turbolinks, vanilla JavaScript Front End Notes: “Our application is an external tool as most of the pages are visible to visitors without an account. We wanted to build the website without any issues for SEO so we just did not bother adding anything fancy. And also when we started there was no vue.js or react. AngularJS was the new fancy tool but seemed like overkill.” - Razvan

Back End: Ruby on Rails Framework, PostgreSQL, jQuery Back End Notes: “We loved the simplicity of RoR when we built it so we did a fast website to showcase our designs. We built it from there. No need for a NoSQL database, we only have caching and postresSQL.” - Razvan

Front End Output: MailerLite for sending newsletters

Front End: TailwindCSS Maker Front End Notes: Both web apps NoHq.co and the newest app is built with TailwindCSS. This Maker decided to use TailwindCSS because “went with whatever you’re most comfortable with, not what’s the most cutting edge...and when using tailwind ⭐️ “don’t forget to include a small JavaScript snippet for toggling the mobile navbar. Always forget it:)”

Back End: Python, Django, Gunicorn, Nginx Maker Back End Notes: This Maker said, “For Django: ⭐️ remember to set up SMTP servers or Sentry or you won’t realize that there are issues on your site.”

Front End Output: SendGrid, Mailchimp/Mailjet, Stripe, Memberstack (only nohq.co) Maker Front End Output Notes: SendGrid for email, Mailchimp/Mailjet for Newsletters, Stripe and using Memberstack (only for nohq.co)

Front End: Next.js 2.0 Front End Notes: Web app built with Next.js 2.0 (open source)

Back End: Now 2.0, Express, Bull, Redis Labs Back End Notes: Hosted on Now 2.0 (Sid is on the $15 plan), API built with Express (open source), Queues managed by Bull (open source), Queue

Front End Output: SendGrid, Sentry Front End Output Notes: Emails sent by SendGrid (free tier), Errors go to Sentry (free tier)

I created a working app with no code! To use it click the button below. I also send weekly emails with new stacks, tools, product comparisons, Maker reviews and ratings. Sign up for my newsletter and I'll be happy to help you make something. Get STACKS sent to your INBOX.

Front End: Typeform

Back End: Zapier, FancyHands Back End Notes: It’s tied together with a Typeform form and Zapier, using a custom developer integration Levels built on his own.

Front End Output: Telegram Credit Zapier Blog for this information.

Front End: App: Android (Android SDK, Firebase SDK)Maker Front End Notes: App: Android (Android SDK, Firebase SDK) Web landing page: HTML + CSS, based on Bootstrap Web version of the app is not in the works yet.

Back End: Firebase (Firestore, Functions, Hosting) Maker Back End Notes: Firebase (Firestore, Functions, Hosting)

Front End Output: App notifications Maker Front End Output Notes: No email or other front end used besides the actual UI of the app or app notifications.

Front End: Typeform, Import.io Front End Notes: "The team first used Import.io to parse the car pricing data, and put it in a Google Sheets spreadsheet. We were abe to get publicly available information about car pricing and make it easily searchable, but they didnt have that tech in the beginning so they turned to automation with import.io." " Then they built a Typeform form where customers could send in a car pricing inquires and used Zapier with email automations to send notifications to their team to find care pricing for users."

Back End: Google Sheets, Zapier, Mandrill, Manual work by Human Back End Notes: "They'd planned to build a Mandrill integration with Zapier to automatically send out car pricing, but for Startup Weekend their team was manually checking prices -the only part of the process not automated."

Front End Output: Mailchimp Front End Output Notes: "They'd planned to build a Mandrill integration with Zapier to automatically send out car pricing, but for Startup Weekend their team was manually checking prices - the only part of the process not automated."

Credit Zapier Blog for this information.

Front End: Strikingly, Typeform Front End Notes: "The Kollecto experience starts with the Typeform form, where customers select their favorite types of art and enter their contact details."

Back End: Zapier, Google Sheets, Google Scripts, Human Task, Survey Gizmo, Pipedrive Back End Notes: ""Zapier then sends that data to a Google Sheets spreadsheet, where Google Scripts help categorize users and show which art types to recommend."" ""Art advisors on the Kollecto team then add art to a SurveyGizmo survey and their Campaign Monitor emails include a customized link to the survey...(for ea customer)"

Front End Output: Campaign Monitor Email Front End Output Notes: ""Art advisors on the Kollecto team then add art to a Survey Gizmo survey, and their Campaign Monitor emails include a customized link to the survey that sends each customer to the new art that'd fit their profile based on the Google Sheets data."

Credit Zapier Blog for this information.

✔ Explore the best no-code tools ✔ Learn how to build powerful applications ✔ Get hired in no-code companies or non-tech roles

Front End: Webflow Back End: Airtable, stripe, zapier, Slack Front End Output: Convertkit, Webflow

Fron End: Wix Front End Notes: Notes from the Maker: “Wix is the website build I chose to go with since I could get the website up in just a few hours. I chose Wix because they offered ecommerce and membership features.” - Dianna

Back End: Mailchimp “My project is mainly based around a newsletter. Mailchimp takes care of that easily for me.” - Dianna

Front End Output: Mailchimp Budget Meal Planner users get weekly 7 day planned meals every Friday.

Front End: Bulma Maker Front End Notes: This Maker decided to use Bulma because at the time of development was the most comfortable “went with whatever you’re most comfortable with, not what’s the most cutting edge”

Back End: Python, Django, Gunicorn, Nginx Maker Back End Notes: This Maker said, “For Django: ⭐️ remember to set up SMTP servers or Sentry or you won’t realize that there are issues on your site.”

Front End Output: SendGrid, Mailchimp/Mailjet, Stripe Maker Front End Output Notes: SendGrid for email, Mailchimp/Mailjet for Newsletters, Stripe,

Front End: Bulma Maker Front End Notes: This Maker decided to use Bulma because at the time of development was the most comfortable “went with whatever you’re most comfortable with, not what’s the most cutting edge”

Back End: Python, Django, Gunicorn, Nginx Maker Back End Notes: This Maker said, “For Django: ⭐️ remember to set up SMTP servers or Sentry or you won’t realize that there are issues on your site.”

Front End Output: SendGrid, Mailchimp/Mailjet, Stripe, PayPal Maker Front End Output Notes: SendGrid for email, Mailchimp/Mailjet for Newsletters, PayPal,

Front End: Bulma Maker Front End Notes: This Maker decided to use Bulma because at the time of development was the most comfortable “went with whatever you’re most comfortable with, not what’s the most cutting edge”

Back End: Python, Django, Gunicorn, Nginx Maker Back End Notes: This Maker said, “For Django: ⭐️ remember to set up SMTP servers or Sentry or you won’t realize that there are issues on your site.”

Front End Output: SendGrid, Mailchimp/Mailjet, Stripe Maker Front End Output Notes: SendGrid for email, Mailchimp/Mailjet for Newsletters, Stripe,

What will you make? Get your free side project stack and let us know what you think!