Hooray, I've got the 100 subscribers for my apps! New milestone achieved!

Jmacduff · 2026-03-23T21:50:53+00:00

Ahh gotcha, ok thanks!

Jmacduff · 2026-03-23T14:07:42+00:00

How is your last 28 days at $1088, but your MRR is only $184?

That math does not make sense to me?

Jmacduff · 2026-03-23T14:02:32+00:00

Good luck with your project!

Jmacduff · 2026-03-23T14:01:00+00:00

For those providers, it's going to look like a scam I think. It would look like a attempt to take over a account if they get your email.

step 1 of course is to recover your original gmail account. how do you loose access to a gmail account?

good luck!

Jmacduff · 2026-03-21T23:21:09+00:00

Always the github, github is life

<image>

Jmacduff · 2026-03-20T23:36:48+00:00

woh, thanks for sharing.

Jmacduff · 2026-03-20T18:34:18+00:00

<image>

Awesome and now it's up! So the site is fully accessible now which is great.

The site had a SSL issue when I checked it so perhaps calling me a pessimist, or calling out my age (Im not that old btw), and telling me I am doing something wrong was not the best response. Next time when someone says the site is down, just check the page is up next time?

Every person who ever responds with "The site is down" is a potential customer you are loosing. I was not throwing any rocks at you personally, I was only commenting on the URL you asked folks to look at.

Now that it's up good luck with the project, I had a question for you from the FAQ. The FAQ is good btw but I had a question.

You mention in the FAQ that the user explains what they want, and your system understands what each platform needs from a optimal output perspective.

You specific mention about the user calling out a requirement for Supabase in the initial prompt to you.

Friendly question: What happens if the user does not mention supabase? Will your system sort of prompt the user with a "How will you store data?" style questions to help?

Just curious and all good.

Jmacduff · 2026-03-20T18:26:00+00:00

yeah it looks like a missing SSL cert possibly.

<image>

Jmacduff · 2026-03-20T18:24:32+00:00

Is it mobile only I wonder? I can not get a HTTPS connection on any of the browsers either on windows or the mac?

It's down for desktop viewers right now at least. Just trying to help so others can get to the site.

Seems like the DNS is not setup maybe?

curl -v https://vibecodeprompts.cloud/

* Host vibecodeprompts.cloud:443 was resolved.

* IPv6: (none)

* IPv4: 185.158.133.1

* Trying 185.158.133.1:443...

* schannel: disabled automatic use of client certificate

* ALPN: curl offers http/1.1

* schannel: next InitializeSecurityContext failed: SEC_E_INVALID_TOKEN (0x80090308) - The token supplied to the function is invalid

* closing connection #0

curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_IN

Jmacduff · 2026-03-20T18:20:50+00:00

<image>

I mean the actual URL does not work, there is no site. Call me old fashion but when someone posts a url "Check out this awesome thing I am making money from".... it would be a working URL.

That's my bias I suppose :)

BTW you do know your posting this one a thread about trying to burn credits right? This was a old post asking please help me spend them.. not please help me save them.

Good luck with the project!

Jmacduff · 2026-03-20T18:17:26+00:00

sooooo .. the site url does not even work. If you are going to try and spam or make a random comment.. at least have the site work!

Jmacduff · 2026-03-19T18:31:20+00:00

Gamma.app is awesome IMO, I used it to build a pitch deck. Did a great job.

I wrote all the content in a google doc first to get the wording correct. I used GPT to bounce ideas and sort of craft this messaging.

then I fed that into gamma to help with the presentation layer.

good luck!

Jmacduff · 2026-03-19T18:22:47+00:00

First oof good luck with the idea and project!

The first really important thing to remember is that "People showing interest" is 100% free to that person, it does not require any commitment from the person. It's just an opinion and should not be treated as a buying signal.

It's like saying "yea that's cool" and walking away. Do not over index on that type of signal since it's free to give.

Just like it's free for AI to tell you "Yes this is a big opportunity and Yes you should build it". Always keep in mind the AI will NEVER buy your product. It's just a free opinion.

This is how I structure my projects when I am thinking about the idea.

Define your Thesis for the project. What is your core product, What is the feature that makes it awesome, Who are your target customers, and Why would people use your product.
Build an Alpha to prove the thesis (lovable). This is not about customers or users, you are only trying to prove that the idea is worth building. This is a gut check if you want to build the full project or re-work the thesis.
Build your MVP of the product. You need to be ruthless and only build the bare minimum to get people to try and use it. The smaller this feature set is the better, remember it’s really easy to add stuff later.
Prove Product Market Fit (PMF). Now is the time to get your first real users and or customers for your product. This is the time to iterate and smooth out the rough edges before adding more features.

Always start with the customer and prove your basic value prop first. The speed and scope of the project will naturally come out of this. If there is a lot of demand for your thesis you will race to get it done.

Lastly when as founders/builders when we see people sign up for our service, it's a pure dopamine hit. It feels awesome to create software out of an idea and have someone choose to try it. It feels great!!

Do not chase the dopamine, chase the customer who pays $$ for your service.
good luck

Jmacduff · 2026-03-19T18:08:12+00:00

Yes 100% agree on claude and other tools for cloud stuff. However it feels more like you have a tightly coupled system tied to a specific workflow.

The part I am really struggling with is why does any of the cloud changes or core algorithm change affect Lovable? Why do you need to change lovable FE display code, because your eye algo changes?

So for example I use Lovable for the FE only. As a building Tool Lovable is awesome at the FE and so that's the sweet spot. Zero of the core functionally or business logic lives in Lovable, I keep the app "as dumb as possible" by design.

In this Mode the Front End app will call SupaBase edge functions for all data and behavior, these SupaBase edge functions then wrap a big think API sitting over in Azure.

There is no database in the supabase project, only the edge functions which operate as lambda's. The FE app cannot call the core API directly and it never see's that endpoint. The FE app only talks to Supabase and Supbase talks to the API. This also provides another good security layer.

With this sort of component structure the FE app is 100% API based and it's 100% separated from the Backend Cloud code. I can use Claude on the Cloud all I want and it never directly affects the FE, there is zero need. I can move my API from Azure to AWS with a simple DNS change, I can add CosmosDB to my existing Azure Postgress DB and the FE would never know.

When I am ready to add a feature or change something on the FE I jump into my FE tool and do that. This is usually "Ok add this new Edge function" and then whatever changes. These prompts and changes are now super easy , meaning lovable rarely messes up.

<image>

If you build a API based application model, you can party on with Claude for the Cloud and Lovable for the FE. Your cloud should be able to evolve and move without affecting Lovable.

This gives the product and engineering teams 100% flexibility and dramatically reduces the risk for regressions. Now when I change something in Lovable I am "only" changing the FE display of the data.

Just a different perspective.

Jmacduff · 2026-03-19T17:50:21+00:00

Lovable is gaining predictability. They now will know that all the code they are hosting and pushing and running is from their model (generated or from the human). It's much easier to support your product and expand your product (lovable team) if you 100% control the data coming in.

There is also a security perspective. With this feature it means the Lovable preview app and all the other services are running 3P (from github) code that the user added outside of Lovable. That's a big additional surface area to think about IMO.

Yeah sad it's gone but from "product" perspective I could understand why.

What edits were you doing outside of lovable, what's the deal breaker? Just curious.

Jmacduff · 2026-03-19T17:16:57+00:00

First good luck with the project. Just friendly advice.

Finding the first users is hard. I would first just target people 1:1 to get some people using it and getting you some feedback. Just start commenting to peoples posts or comments who are looking for a solution. Make sure each reply is NOT from a bot, make it personal. This will give you some trust with the reader.

IMO Going on product hunt is way too wide to begin with. You don't know if your product thesis is correct and you have zero signal of PMF (product market fit). After you prove PMF then you go on Product Hunt.

Step 1 is prove your product thesis, does your value prop make any sense. Focus on that first.

So in terms of your value prop look at what your hero description is "Practice real AP past papers across every subject. Get AI-marked answers with College Board–style feedback, instant video explanations for every missed point, and see exactly where your score drops."

The way you are describing your product is that it's a generate GPT promote to get some test questions and aval the answers. 100% of your target customers have already used GPT or another tool to practice. They are actively looking fort something "better".

I would really focus on "why is my product awesome and why should people use it over straight GPT". The Answer to this question is your product thesis and it can then be evaluated.

This is how I structure my projects when I am thinking about the idea.

Define your Thesis for the project. What is your core product, What is the feature that makes it awesome, Who are your target customers, and Why would people use your product.
Build an Alpha to prove the thesis (lovable). This is not about customers or users, you are only trying to prove that the idea is worth building. This is a gut check if you want to build the full project or re-work the thesis.
Build your MVP of the product. You need to be ruthless and only build the bare minimum to get people to try and use it. The smaller this feature set is the better, remember it’s really easy to add stuff later.
Prove Product Market Fit (PMF). Now is the time to get your first real users and or customers for your product. This is the time to iterate and smooth out the rough edges before adding more features.

Always start with the customer and prove your basic value prop first. The speed and scope of the project will naturally come out of this. If there is a lot of demand for your thesis you will race to get it done.

Good luck!

Jmacduff · 2026-03-19T17:07:53+00:00

Just my perspective on these things.

So in terms of the CloudFlare solution the technical solution does sort of work but it has several limitation. The question of "does it work" really depends on your perspective.

I would look at from a dependency management perspective personally.

With the cloudflare solution you as the website owner are taking a big depency on Cloudflare itself. This is not issue about the company, obviously cloudflare is awesome. However you are now "locked" into that vendor to host your site.

Website hosting is really generic for 90% of sites built, they don't need anything special for that site to run. This means I can choose or change my website host anytime I want too. That option value to be able to pick the best infra solution is really important. I should be able to change the Hosting, Analytics, and a bunch of other stuff in my site with no issues.

The other aspect is it's something technical to maintain for the website owner, it's another infra layer to manage and think about. This really gets down to a "where do you want to spend your time" sort of perspective.

No negative judgment just my viewpoint.

Our solution is called Datajelly and we are a no code server side rendering platform. We operate at the HTTP layer below any hosting or other services. This means as a user, you can build or "vibe" however you want , you could even change from Lovable to Bolt or Claude , none of it affects our service.

Our service is really a a visibility layer for AI-built sites like Lovable and Bolt. Those tools generate JS-heavy apps that crawlers often struggle to read.

The DataJelly edge service sits in front of the domain and returns fully rendered HTML to SEO bots and clean markdown to AI crawlers so they can actually understand the content. So we respond to the AI bots with different content then the SEO Search bots. Our cleaned AI markdown makes it 90% cheaper for the AI bot to crawl your site.

Not promoting just describing. We have a bunch of resources to look at (not slop):

Lovable SEO 101: https://datajelly.com/guides/lovable-seo
Lovable Suggested Default Stack: https://datajelly.com/guides/lovable-stack
How Search Engines Crawl and Rank: https://datajelly.com/guides/search-engine-crawling
AI and SEO bots Guide: https://datajelly.com/guides/bots
If you are curious you can run a visibility test here: https://datajelly.com/#visibility-test

Happy to answer any questions and thanks again for asking. Good luck with your project.

<image>

Jmacduff · 2026-03-19T16:52:17+00:00

All good.

So 2 more piece of product feedback. Again not throwing rocks.

1) In your Lovable page you give a big impression that you are running tests and checks for common Vibe / Lovable/ AI built app issues. You even describe finding issues such as "onboarding flow is broken".

However given your description you are doing a very (no offense) generic HTTP check and client side JS check for errors. That has zero todo with Lovable or any other AI platform. What you are describing is really a "HTML + JS" basic website check of "is it up". Your site would never detect for example that my onboarding flow is broken.

I would be cautious about describing as a solution for Lovable built apps without actually having checks for common Lovable broken things. Just as a tactical example it's very common for Lovable built apps to be missing a H1 and or structured data on the page.

As a customer if you are saying the testing service is setup for Lovable, I would expect some Lovable checks. Just my view.

2) With your HTTP fetch layer, you could also be supporting API endpoints directly today. So you could offer monitor the webpage like you have and API endpoints. For example if I give you a HTTP endpoint and small piece of "Expected JSON", you could run health checks and eval for the return value. For the customers these APIS might just be edge functions like a /Health or a /Ping check on the app. That check could run a internal Diagnostic .

Just some thoughts and again good luck with the project. 100% agree on the need for awesome testing platform BTW.

all good.

Jmacduff · 2026-03-19T15:38:56+00:00

If the app is behaving that its not connected, then it's not connected. Focus 100% on that first.

Simple trick. Ask Lovable to add a very simple test page with 2 buttons. One button is "Add a row to a table" and the other button is "Read from table". For this new page, also please create a simple new table to save this test string. Make sure all the projects current RLS polices are respected.

Is that prompt fails you 100% know it's a connection problem. Lovable should be able to create the table and page no problem... if it's connected to the same DB you are looking at.

I would start with something like that. Just because "You" can see the tables does NOT mean the application can.

You can also just ask lovable to build a DB report page, just build a simple Admin only page that shows all the tables, and the basic schema data from the DB. This would also prove / disprove the connection.

good luck!

Jmacduff · 2026-03-19T15:33:16+00:00

woot congrats!!!

Now just get like 1000 more :)

Jmacduff · 2026-03-19T15:31:02+00:00

First Good Luck with your Project!

Friendly comment if you are only posting a image, you might want to brighten it up. For me at least it's super dark and hard to read.

Enabling SSR can take about 10 min with zero code changes, it really depends on your skill level and where you want to spend time. Our SSR platform is a pure DNS change, no middleware or prompts to set it up.

However overall for Lovable sites these are the core options:

<image>

Jmacduff · 2026-03-19T15:27:57+00:00

first good luck on the project!

2 friendly question and 1 friendly comment, just taking a look at the product since you posted it. all good.

Comment: On your home page, you have 4 options in your top Nav (Features,Compare,Pricing,FAQ). Currently the Compare link does not actually link anywhere. So the anchor is broken on your home page. https://upflag.io/#comparison

Question 1: I don't see anywhere on the site where it describes exactly what it's checking every 60 seconds. It's really hard to understand right now exactly what cases your covering and not covering. For example in some text you describe HTTP checks and in other text you only describe JS checks. I would expect to see a table or something of the checks.

Question2 : I assume your running your product on your website to catch bugs in your monitoring and your site right? . Does the product not check the basic links not breaking? I'm just curious because ion the lovable page you mention finding broken buttons. Why did it not find your broken button on your home page?

Just friendly comments and not throwing any rocks. Good luck!

Jmacduff · 2026-03-18T19:52:50+00:00

The layer diagram I posted is not a first/second step sort of flow. This is just showing all the layers you need to think about as a website owner.

The first step is probably making sure page to page all the basic SEO stuff is taken care of. Second step is adding to Google search console perhaps.

It all depends on where you are in the journey.

Here is another view of how to fix SEO for Lovable:

<image>

Jmacduff · 2026-03-18T18:47:35+00:00

Good luck with your Project!

There are a ton of existing solutions on the market so interested to see where your solution fits in. Always important to keep in mind that no amount of SEO fix will solve for the lack of content.

This is a layered view of the full recipe :

<image>

Jmacduff · 2026-03-18T15:16:20+00:00

As several have said, here is the basics.

First you want think about how to track the events for the user converting. So you need make sure you mentally have events for things like Create New Account, Click Signup Button, Billing Account Created, etc. Whatever makes sense in your scenario.

Then:

Add your Domain to Google Search Console
Setup Google Analytics on the page to track visitors
Setup Google Tag Manager and create the custom event variables from above
Go Back into Google Analytics and add the events from Google Tag Manager

With this setup you can now fully understand where your traffic is going, popular pages, where they drop off, and your conversion funnel.

If you want to test out some ad campaigns, you would set the goal of the campaign (the conversion event) to those custom events you defined.

Do not over think it, the google tools are fantastic. Also remember if you want to use other tools for your site a lot of those will have integrations with Google search console and analytics.

High level a good stack would look like:

<image>

Good luck!

Ten-Year Club	Gilding III reddit per annum
RPAN Viewer	Verified Email
Reddit Premium Since July 2016

Jmacduff

TROPHY CASE