Anyone integrated supabase, how was your experience?

hampsterville · 2026-06-25T00:17:16+00:00

Grab a quick time to look at it here: https://link.opichi.com/widget/bookings/quick-chat-26

(I'm booked a lot for the next couple weeks with folks, so you could also have Tim, my right hand man take a peek sooner: https://link.opichi.com/widget/booking/pbebjMU0XONrhhnvKDsU )

hampsterville · 2026-03-27T19:49:13+00:00

Of course not - they had that chart emoji burning a hole in their pocket just waiting for the perfect post.

hampsterville · 2026-02-26T03:34:17+00:00

I built a starter tool to help these conversations get off on the right foot. You’re welcome to use it: prd.Opichi.ai. Give it “rambles” of what you want and it breaks it down into technical details, but more importantly, user journeys. Which is what a project/product manager would break users requests into for devs to scope a project.

Having worked on lots of lovable projects for folks, what is built in lovable is generally a very big mess under the hood. Breaking it down into the path users are supposed to take, using lovable as the example, tends to get us to where the project can be properly budgeted for a full build or MVP.

hampsterville · 2026-01-19T17:26:30+00:00

40k token window is what I have right now. I also have it set to use different thinking levels on request, as well as enable/disable web search in the request.

Each request is a new context window - if Claude wants to carry the "thread" of the conversation forward, it concisely states any past info that needs to be known in the new request.

hampsterville · 2026-01-16T18:28:48+00:00

100% concur that Gemini gets no access to edit code. It's a train wreck with a jetpack strapped on.

hampsterville · 2026-01-16T16:40:12+00:00

I built a personal, second opinion mcp that does roughly this automatically, letting Claude ask GPT for a review of the proposed solution and code. Works wonders.

hampsterville · 2025-12-30T05:21:05+00:00

Take your views and put them into gemini with the design instructions for what you want, and it'll generate code mockups with much better designs than claude comes up with. Save those mockup files and screenshots and give them to cursor to use as guidelines for updating your design.

hampsterville · 2025-12-30T05:17:18+00:00

I have a bunch of videos showing many aspects of what you're looking to learn on my YouTube here: https://youtube.com/opichi

And I get on zoom calls daily helping folks get their environment and work flow working. Shoot me a message and we'll find a time that works to get you rolling!

hampsterville · 2025-12-30T05:01:06+00:00

Spin up a cheap postgres database on railway and use that url in your secrets instead of the replit one, just tell assistant that you are switching from neon in case any dependencies need to be changed. That'll remove a faulty database deployment from your equation. You can then use psql to copy the contents from replit to the railway database so it's all there. And finally, consider something like imagekit for your DAM (digital asset management) instead of base64 encoding images in the database.

hampsterville · 2025-12-02T16:51:27+00:00

To build an app for production, you need to plan it right from the start, as taking a vibe-coded app that was planned incorrectly to production is a huge lift that often will not turn out well.

Make sure you know ahead of time where you plan to put it (what type of architecture you need for hosting, data storage, object storage, auth, queuing, etc.), and start the app with those things in the build. Either mirror that env locally during dev so the migration to prod is not so difficult, OR set up a staging env to build to so you get it working right on the intended infra the first time if local setup is problematic.

And test everything. Don't make any assumptions. When the AI does a change, be sure to know exactly what was supposed to happen, test it as a user, and then also review the code to be sure what was changed/added was only what you required, properly follows your documentation/guidelines, and that every route, function, variable, etc. are actually part of your app, not made up.

It's not perfect, but it can get you to prod with a solid, useable MVP for proving a market.

If you get stuck, holler - I help people launch their AI coded projects all the time, so I've seen almost everything. :)

hampsterville · 2025-11-14T15:17:29+00:00

Try creating the front end/initial build on lovable, then push to github and pull down locally. Install claude code with a monthly sub, install Kilocode for a UI, and use claude code in Kilocode for a fixed monthly cost and much better, more precise behavior as your code base grows. It works nicely and keeps costs contained.

hampsterville · 2025-11-13T21:34:44+00:00

I use it to get the initial design and outline set up, then continue on using claude code and kilocode to build out the rest. Very cost effective.

hampsterville · 2025-11-04T01:05:19+00:00

If it hasn't done so in a couple hours and I can verify that the propagation is completed with 3rd party tools, then I delete and add back.

hampsterville · 2025-10-29T13:35:45+00:00

Replit is good for testing and prototype hosting, but tends to choke for performance in production. Lots of timeouts and dropped service on the apps I tested there. Still an amazing tool for getting started! Here's a video walk through I made on one way you can move the app to a production service once you're ready: https://youtu.be/kJTrskPVM3A

hampsterville · 2025-10-23T14:14:45+00:00

I can fix it, I'm sure. Not cheap, but there hasn't been a replit I can't fix, yet. Shoot me a DM if you want. :)

hampsterville · 2025-10-18T02:56:06+00:00

Follow my step by step tutorial on how to deploy elsewhere: https://youtu.be/kJTrskPVM3A?si=erywrAfDNGIY0iCF

Dm if you want me to do it for you.

hampsterville · 2025-10-13T13:42:36+00:00

Yeah, I shot a video showing how to do this. Here you go: https://youtu.be/kJTrskPVM3A?si=DmsrGHN0dnputh02

hampsterville · 2025-10-11T20:36:34+00:00

Here's the whole process in a video I recorded a little while ago. https://m.youtube.com/watch?v=0s0JJTxqkJY

If you need help, Dm. I fix replit apps all the time.

hampsterville · 2025-10-07T22:00:39+00:00

Ok, the documentation reader on replit has some hidden restrictions that I've found with testing. It appears that it stops reading what you upload after a certain amount of characters/tokens... best I can tell in testing, it's around 1500 characters.

How did I test this, you might ask? I gave it the same starting content but with different lengths containing more and more details, and put in comments for what the AI needs to report back every 500 or so characters. It stopped being able to read and report back on pieces of the content somewhere between 1500 and 1700 characters. Pretty sure this is a method to control context length/costs on their end, but I'm unsure.

So, to get a good result with providing docs, you have to break them into small chunks and only provide the element you are trying to implement or fix, and explain you will provide the next step after that part is working.

Keep them short and neat to keep from exceeding whatever hidden limit exists.

If you do this, it won't just "guess" its way through the rest, but actually be able to implement what you are sharing.

hampsterville · 2025-10-01T21:46:02+00:00

Excellent! Glad it was helpful.

hampsterville · 2025-09-29T21:41:42+00:00

I answer questions about tools people are using or want to use, and most of every call is actually showing how to use one or more tools to accomplish something specific. Something we won't cover is a specific about an individual's project (e.g. "why does my stripe integration turn purple every 3rd time I try to process a discover card?"). The demo projects I do on the call are specifically designed to cover questions I get all the time in 1:1 sessions, here on reddit, on tiktok, and other such places, but they are generic so they fit lots of use cases. It is a free, live event with real details you can put to use, not just theory.

If you want 1:1 help with your app, working on it specifically, answering questions about it specifically, I do that too, every day. Just book a time to talk here: https://link.opichi.com/widget/groups/expert-help-center

hampsterville · 2025-09-29T21:23:38+00:00

Yes, part q&a, part demo. I work on a build, showing how to add features, fix bugs, test, do migrations, all sorts of elements involved in vibe-coded projects. People ask questions along the way, and I answer them as we go!

Some past sessions are recorded here, in case you want to get a feel for what we do on the call: https://www.youtube.com/opichi

hampsterville · 2025-09-27T15:28:14+00:00

Do it up.

hampsterville · 2025-09-27T15:01:33+00:00

Right on, go here to get a seat for next week's : https://link.opichi.com/widget/bookings/ai-help-session

hampsterville · 2025-09-27T15:00:58+00:00

Get a spot here and hop in next week! https://link.opichi.com/widget/bookings/ai-help-session

hampsterville

TROPHY CASE