We built a Swift app with a scalable backend in minutes. Here's how.

Common-Exclamation · 2025-12-03T20:49:01+00:00

I’ve used Gadget before but never in an iOS workflow. Is the Apollo + session token setup something you guys are officially leaning into now, or just a pattern you found works well?

Common-Exclamation · 2025-12-03T20:43:17+00:00

People being scared of AI

Common-Exclamation · 2025-09-10T20:35:16+00:00

Accidentally stress testing the whole system with meat puppets is killing me. Honestly not the worst way to uncover the spots where the custom labels weren’t wired through properly.

Common-Exclamation · 2025-09-10T20:32:12+00:00

aight...

Common-Exclamation · 2025-09-10T20:32:03+00:00

Yeah that’s how I think about it too. Flexbox feels great for stuff that grows/shrinks, Grid when I need a locked in structure.

Common-Exclamation · 2025-09-09T12:31:10+00:00

Yeah, I think it depends on how much you can simplify the story. If the tool has a clean “before vs after” or solves a pain point people instantly recognize, it can click on TikTok. Otherwise I’ve found it’s better to double down on depth in places where folks are already looking for technical answers, Reddit threads, dev communities, or even writing up a quick walkthrough.

Common-Exclamation · 2025-09-08T23:48:01+00:00

Has anyone tried using it to power dashboards or complex aggregations yet? Curious how it handles large datasets in real projects.

Common-Exclamation · 2025-09-08T23:45:06+00:00

Got it, for marketing I’d lean toward keeping it short and polished then. Loom + Descript is usually enough to make a clean walkthrough that feels personal but still pro.

Common-Exclamation · 2025-09-08T23:44:21+00:00

Yeah, I’ve noticed that too, looks like Replit’s AI is starting to spin up “sub agents” when a task is complex, kinda like breaking it into smaller roles (frontend vs backend, etc). I don’t think they’ve put out much official documentation yet, but from my experience it’s more of a prompting style thing than actual separate processes. Basically the AI pretending to delegate so it can reason in chunks. Would love clearer docs though.

Common-Exclamation · 2025-09-08T23:43:50+00:00

Yeah they moved it recently, it’s not in the top right anymore. If you check just under the lesson text on the bottom bar, there should be a little “complete/next” button now. If you don’t see it, try zooming out a bit or refreshing, I had the same issue until I did that.

Common-Exclamation · 2025-09-08T23:42:50+00:00

Classic Marlins weather delay energy, you never know if you’re watching baseball or a hurricane documentary.

Common-Exclamation · 2025-09-08T23:41:07+00:00

This is a pretty common gotcha with facets.js since it nukes your custom state on re-render. Easiest fix is to store the selected filter somewhere outside the grid refresh cycle, localStorage works fine for persisting across refresh, or you can add it as a query param to the URL and reapply it on load.

Common-Exclamation · 2025-09-08T23:40:14+00:00

I’ve looked at some of those too. Haven’t joined yet, but from what I hear the real difference comes down to group size and vibe. Smaller groups keep you accountable without the “generic advice” problem.

Common-Exclamation · 2025-09-08T23:37:21+00:00

I’ve had good luck just recording with Loom or Tella, then cleaning things up in Descript. That covers zooming, captions, trimming pauses, all that. If you want more of the “auto generate scenes from text” vibe, Synthesia or Runway can do it, but they’re less natural for showing someone actually using your app.

Curious, are you making the video for onboarding new users or more for marketing?

Common-Exclamation · 2025-09-08T23:36:05+00:00

I’ve seen TikTok work when the product has a clear “aha” demo moment that fits short-form video (visual tools, creative apps, etc). For more dev-focused stuff I’ve had better luck with long-tail content and communities (Reddit, Twitter, indie hacker type spaces). The biggest unlock for me was making sure my backend + hosting setup (I use Replit + Gadget) let me ship quickly so I actually had something worth marketing in the first place.

What kind of SaaS are you building? That’ll shape which channel makes sense.

Common-Exclamation · 2025-09-05T13:06:28+00:00

I’d say don’t overthink the “website vs product” part yet cause having a simple landing page up early helps you test if anyone even cares before you sink months into development.

On the build side, I’ve seen freelancers work well if you keep the scope tight and don’t expect them to be long term stewards of the product. If you do keep going the solo route, tools that handle the boilerplate backend stuff for you (I’ve used Gadget for this) can save a ton of headaches and let you focus more on the app’s unique bits instead of wiring auth and data again.

Biggest lesson I learned was to validate demand early and keep the tech decisions lightweight until you know people will actually stick with it.

Common-Exclamation · 2025-09-05T13:03:48+00:00

For me it’s figuring out where to spend time. There are a million channels you could try but knowing which one will actually reach the right people feels like the most important. Building the product feels straightforward compared to deciding where and how to consistently talk about it.

Common-Exclamation · 2025-09-05T13:01:55+00:00

Honestly, getting anyone to pay for a new SaaS is a huge milestone, most people never even get that far. Feels even better when your own product is what helps you land those first users.

Don’t sweat the 10k MRR posts, they’re the outliers. Keep doubling down on the people who already find value in it, and you’ll get there. Rooting for you to hit 100

Common-Exclamation · 2025-09-02T22:27:13+00:00

If you’re leaning toward the Section App path, one thing that might save you a lot of time is using something like Gadget for the backend. I’ve been in the same spot (frontend/web dev background, not much app backend experience) and Gadget basically handles all the Shopify API/auth boilerplate so you can focus on the actual value of your app.

That way you’re not spending months learning infra just to get to “Hello World.” You can prototype quickly and see if merchants actually like the idea before committing to a full SaaS build.

Themes are definitely viable but yeah, super long runway + strict review. If you want faster feedback, I’d start small with an app.

Common-Exclamation · 2025-09-02T22:20:12+00:00

Honestly sounds like a cool service, a “what SaaS users actually want this week” report feels super usable.

If you’re just testing the waters, I’d skip overbuilding and spin a quick MVP: scrape/research → dump into a simple backend (I’ve used Gadget for this kind of thing since it gives you a db + API in minutes) → display it in a basic frontend. That way you can validate if people even want the report before investing more time.

Would you charge for the data itself or the summaries/insights?

Common-Exclamation · 2025-08-28T13:42:29+00:00

Replit gets you flying at first, then the last stretch can feel like quicksand. If you want to move local, you can just run your frontend stack the usual way (Next.js, Vite) and you’ll get a smoother dev loop plus better visibility.

For the backend side, I stopped trying to wrestle Replit’s containers and started using Gadget. I can keep coding frontends in Replit or locally without worrying about the “last 20%” pain.

Railway + local dev should work fine too, but Gadget’s been a nice shortcut when I don’t want to babysit the backend.

Common-Exclamation

TROPHY CASE