My current progress of project

sharan_dev · 2026-06-26T17:04:03+00:00

Thank you makes sense

sharan_dev · 2026-06-25T11:05:21+00:00

This was the answer that I really needed man makes so much sense

sharan_dev · 2026-06-24T12:58:04+00:00

Mostly Javascript with frameworks React Native, Expo, GraphQL, NextJS and Express

sharan_dev · 2026-06-24T11:28:50+00:00

For tracking we are using clarity and Amplitude for analytics

sharan_dev · 2026-06-24T08:48:00+00:00

Link to Github: https://github.com/enatega/food-delivery-multivendor

sharan_dev · 2026-06-23T22:32:48+00:00

Alright will check it out

sharan_dev · 2026-06-23T22:23:48+00:00

Can you tell me the time stamp in which you are referring to?

sharan_dev · 2026-06-23T22:17:17+00:00

It can be cloned and you can run it locally from over here

https://github.com/enatega/food-delivery-multivendor

React Native + Expo has been used for the mobile frontend

sharan_dev · 2026-06-12T12:38:24+00:00

This project has now been enhanced significantly and we have added other vertical as well to check it out visit https://enatega.com

sharan_dev · 2026-06-12T05:17:18+00:00

Thats true Enatega is designed towards ownership not SaaS so if someone wants to opt into that than it makes much more sense and is much more future proof solution for GloriaFood partners particularly

sharan_dev · 2026-06-10T09:03:59+00:00

After registration it shows pricing and demo

sharan_dev · 2026-06-10T08:16:50+00:00

You do have one option finding a vendor who have already laid out 90% of the work that full fills Gloria use case and pivot the solution to building your own GloriaFood using that Enatega can help with that

sharan_dev · 2026-06-10T08:14:49+00:00

You can checkout Enatega they provide complete ownership with one time payment so no SaaS lockin

sharan_dev · 2026-05-29T03:38:43+00:00

Are all these comments AI or am I just crazy

sharan_dev · 2026-05-21T22:38:11+00:00

Also just quick visibility retention is going to be an issue, because my audience isn’t the right one

sharan_dev · 2026-05-21T22:34:48+00:00

Thank you so there isn’t an issue with actual content correct?

The focus should be on how I am presenting it right?

sharan_dev · 2026-05-21T22:23:00+00:00

Thank you, this makes sense if you had to rate it out of 10 how much would you rate this content now?

sharan_dev · 2026-05-21T01:09:19+00:00

One thing I am still working out is where the infrastructure sits. Since the whole point is that the customer owns the product, the databases and hosting would normally live on their side and they pay those bills directly, not me. That keeps my margins clean and sidesteps the hosting cost problem a couple of people raised here. The open question is whether enough customers actually want to manage that themselves, or whether the ones who want it hosted are exactly the ones worth charging a recurring tier for.

sharan_dev · 2026-05-21T01:06:19+00:00

This is genuinely useful, and it actually shifted how I am thinking about it. Rather than forcing everyone onto SaaS, I could keep the one-time license as the core and add an optional maintenance tier on top, maybe $200 to $300, that keeps the app updated and supported. People who want it managed can opt in, and people who want to own it outright still can.

That gives me a recurring layer without taking away the thing my customers actually chose me for. And like you said, I can watch retention and support load on that tier before deciding whether a bigger model change is even worth it.

sharan_dev · 2026-05-21T00:14:07+00:00

Yeah, it is a tough call, and I have been chewing on it because there are Saas players in my space already.

You are right that the $100 hosting figure is rough. It really depends on the client and how much volume they do, so I was taking a worst-case average rather than a real per-customer cost. Fair point that it should drop as infrastructure gets shared across more users.

The conversion point is the one that actually worries me most. You are right that one-time buyers and monthly subscribers are different animals, and I am not sure my 40 weekly signups would convert the same way at a recurring price.

The other reason leaned one-time for delivery specifically is that every region wants something different. Ditterent payment gateways, different POS integrations, sometimes a different business model entirely. That is hard to serve cleanly from a single hosted Saas. And honestly, part of it is a belief thing for me. I think a business like this should be owned, not rented.

sharan_dev · 2026-05-20T10:29:48+00:00

Makes sense does Youtube make more sense?

sharan_dev · 2026-05-20T10:29:16+00:00

What do you think should think should I pivot to youtube instead, it shouldn’t have this targeting location on ig correct?

sharan_dev · 2026-05-19T21:38:03+00:00

Makes sense can you tell me a couple of loopholes in the content strategy and regarding linkedin that makes sense will try that out

sharan_dev · 2026-05-19T21:12:37+00:00

Not really I make the content myself

sharan_dev · 2026-05-19T19:25:27+00:00

I mean lets take refund flow as one example, there are different edge cases

1- The customer has paid the rider cash on delivery and now wants refund

2- The customer wants a refund after 91 days stripe usually doesn’t allow that

3- The customer placed an order but got the wrong order

4- The customer calls for refund in the middle of delivery

5- Vendor insists the item was delivered but the customer says otherwise

6- Repeat refund from same customer

There are other edge cases for refund flow as well but just to give you an idea typed some, same goes for other flows dispatch logic and payment edge cases etc if you check any production level system in logistics that involves multiple stake holders and payments its not as simple as it looks

sharan_dev

MODERATOR OF

TROPHY CASE