next-shopify-starter VS nextjs-subscription-payments

Nice work. I went down this rabbit hole a few weeks ago and built an open source Next.js Shopify Store that hooks up with the Shopify Storefront API. Feel free to check it out: https://github.com/btahir/next-shopify-starter

Here is the link: https://www.doggystickers.xyz/

I also open sourced the code if anyone is interested (its Next.js + Tailwind CSS + Shopify in the backend): https://github.com/btahir/next-shopify-starter

I am open sourcing my Next.js + Tailwind CSS + Shopify starter template. The starter is designed to be super simple but fully functional. There is actually a live store running on it which you can check out here => https://www.doggystickers.xyz/

I used thorwebdev's template to make a fun Next JS app that displays a daily code puzzle.

I used the nextjs-subscription-payment boilerplate for illostration.com. This boilerplate already includes two tables, subscriptions and users. For my credit system, I decided to keep it simple and just add a column for credits on the users table. Now I only have to check for active subscriptions and reset the credits at the end of the month. Each subscription includes the user_id and the amount of credits included.

You can get started easily here by deploying with the template. Here's a larger example.

This https://github.com/vercel/nextjs-subscription-payments/blob/main/utils/useUser.js

Related, free template: https://github.com/vercel/nextjs-subscription-payments

I definitely see where he's coming from. For example I can click the big blue 'Deploy' button on this Supabase example and without writing any code I'll have an application with user authentication, Stripe subscriptions, and a database set in up in no time. Then I can drop in this prebuilt Kanjam board code, wire up state of the board to save to the Supabase database, and BOOM I have a super knockoff Jira in less than a day and written maybe 100 lines of code.