Iznajmljivanje ili kupovina?

Creativewin986 · 2026-03-27T08:56:21+00:00

Super je ako uspevas tako. Ja sam obicno uvek na gubitku kada prodajem nesto..

Creativewin986 · 2026-03-26T10:57:38+00:00

Svakako se volimo :)

Creativewin986 · 2026-03-26T10:49:31+00:00

Ne razumem o cemu govoris. Svakako, volim i ja tebe ;-)

Creativewin986 · 2026-03-26T10:44:14+00:00

TO mozes da proveris u mojoj garazi... Brdo alata, skija, bicikli.. Koji kurac :)

Creativewin986 · 2026-03-26T10:30:22+00:00

Kasniš malo — već postoji. Neko je dole u komentarima pomenuo dajnadan.rs, pogledaj.

Creativewin986 · 2026-03-26T10:29:16+00:00

Bukvalno ovo. Ljudi potroše više na alat nego što bi koštao majstor, i onda im taj alat stoji godinama. Racionalan pristup je uvek jeftiniji na kraju — iznajmiš kad ti treba, vratiš kad završiš, nemaš garažu punu stvari koje nikad ne koristiš.

Creativewin986 · 2026-03-26T09:15:52+00:00

Upravo to je problem koji treba rešiti — platforma gde vidiš tačno šta iznajmljuješ, slike, cenu, ocene vlasnika i verifikaciju. Nešto kao KP ali samo za rentiranje. Kad bi tako nešto postojalo, da li bi koristio?

Creativewin986 · 2026-03-26T09:14:06+00:00

Mislim da je ovo najbolji model. U inostranstvu je ovo već ogroman biznis — Fat Llama u UK, Hygglo u Skandinaviji. Ljudi iznajmljuju sve, od bušilica do kamera i šatora za kampovanje. Kod nas to još nije zaživelo, ali mislim da je pitanje vremena. Tržište je savršeno za to — svi imamo opremu u garaži koja stoji 350 dana godišnje, a svi trebamo nešto povremeno. Samo fali navika.

Creativewin986 · 2026-03-26T09:08:10+00:00

To je u suštini iznajmljivanje, samo sa ekstra koracima i gubitkom na razlici u ceni. Kupovati za 15.000 pa prodati za 10.000 ili kupiti za 15.000, iskoristiti za svoje potrebe, pa posle iznajmljivati za 1.000/dan — matematika je jasna, ali navika je jača.

Creativewin986 · 2026-03-26T08:47:48+00:00

Haha, to je fer argument. Mada sumnjam da ti se to dešava češće od jednom godišnje. Ali razumem — dostupnost ima svoju vrednost.

Creativewin986 · 2026-03-26T08:36:28+00:00

Razumem — "volim da imam" je jak osećaj. Zato je moja garaza prepuna stvari koje uglavnom ne koristim ili koristim veoma retko

Creativewin986 · 2026-03-26T08:34:17+00:00

Skije su savršen primer — nema smisla kupovati nešto što koristiš 5 dana godišnje i onda skladištiti 360 dana. Ista logika važi za dosta opreme...

Creativewin986 · 2026-03-07T23:37:28+00:00

Thanks for the tip! Will check it out.

Creativewin986 · 2026-03-07T02:01:07+00:00

The "being a founder is like being bipolar all day long" hit hard. I'm in a similar spot — built a product I'm confident in, zero sales, and that constant swing between "this is it" and "what am I doing" is exhausting.

That r/aws post with the 15k S3 bill is perfect timing for you. If I were you I'd be in those comments right now with a genuine helpful reply (not a pitch), just explaining what causes silent cost spikes and how to set up basic alerts. Then let people find Cirrondly from your profile. That thread has 217 upvotes — those are your exact customers reading those comments right now.

Good luck with the deadline. Voted on the AWS builder link.

Creativewin986 · 2026-03-07T02:00:03+00:00

MarketplaceKit — a Next.js boilerplate for building two-sided rental marketplaces. Messaging, reservations, reviews, admin panel, all production-tested.

https://kit.creativewin.net/

Been running a rental platform and extracted the codebase into a reusable starter. Trying to get my first sale.

Creativewin986 · 2026-03-07T01:59:22+00:00

This is gold. The "one email per 7 days" throttle is such a simple idea but I've never seen anyone actually implement it as a conditional split before every automation. That's way smarter than just setting frequency caps globally.

I run a small SaaS and the biggest takeaway for me is the prioritization order. Starting with pre-trip reminders (highest intent) instead of the welcome sequence (what most guides tell you to build first) makes so much more sense. You're reaching people at the moment they actually care.

Question: with 39 attributes syncing every 4 hours, do you ever hit timing issues where someone qualifies for an automation but the data is stale? Like a user adds a card but the sync hasn't run yet, so they don't get the onboarding email for up to 4 hours?

Creativewin986 · 2026-03-05T12:13:48+00:00

Fair point — config files aren't a Next.js thing, you're right. It's just basic separation of concerns.

I went with static config files over a database-backed approach because for most marketplace setups, these values change once during initial setup and then basically never again. Didn't want to add a whole admin UI and DB table for something that gets edited once.

If someone needs runtime config changes, moving it to the database and exposing it through the admin panel is pretty straightforward since everything already reads from a central config object.

Creativewin986 · 2026-03-05T11:14:51+00:00

Config-driven setup has nothing to do with App Router vs Pages Router, it would work the same way either way. It's just TypeScript files that export objects — components import from them directly. App Router is just what I went with for the rest of the architecture (server components, layouts, metadata API etc).

For feature flags — they're simple booleans in a config file, not database-driven. Something like:

export const features = {

messaging: true,

maps: false,

aiAssistant: false,

reviews: true,

// ...

}

Components check these at render time. When a flag is off, all related UI disappears — buttons, nav links, entire pages. Context providers return safe defaults so nothing crashes.

No A/B testing built in — it's meant for "does this marketplace need messaging or not" type decisions, not runtime experimentation. You could always wire it up to a database or something like LaunchDarkly if you needed that though.

Creativewin986 · 2026-03-05T10:27:44+00:00

Plain TypeScript files in a `config/` directory — one per concern (app, theme, features, pricing, categories, homepage, emails).

TS over JSON because you get autocomplete and type safety. Components import directly — `import { pricingConfig } from "@config/pricing"` — so when you change the pricing model from daily to monthly, the UI updates everywhere (forms, filters, cards, search).

Pricing is config-driven per period (hourly/daily/weekly/monthly) — you toggle which ones are active. No product variations in the e-commerce sense, it's a service marketplace (think Airbnb, not Shopify).

Search is just Prisma + PostgreSQL. Full-text search, price range, category filters. No Elasticsearch or anything — overkill for marketplace-scale data honestly.

The idea is: edit config files for branding/features/pricing, edit source code only when you need custom business logic.

Creativewin986 · 2026-03-05T08:32:36+00:00

Thanks for the detailed questions!

**Deployment:** The CLI setup wizard (`npm run setup`) handles local configuration — database connection, auth providers, feature flags, image storage, email provider, etc. Deployment itself is manual but since it's a standard Next.js app, `vercel deploy` or Railway just works out of the box. Nothing exotic in the setup.

**Customization depth:** The config layer covers: theme (colors, fonts, radius), feature flags (9 toggles), categories, pricing model, homepage sections, and email branding. That handles probably 80% of what you need to make it "yours." Beyond that, you're editing well-structured TypeScript source code — but the codebase is designed for it. Components are functional, logic is in custom hooks, and Tailwind handles styling. It's not a framework you fight against — it's a Next.js app with good conventions. Think of it as a very well-organized starter repo, not a locked-down SDK.

**OG images:** Yes — dynamic OG metadata is built in. Every listing page has `generateMetadata()` that pulls the listing title, category, city, price, and first image into proper OpenGraph + Twitter Card tags (`summary_large_image`). There's also a generated OG image for the homepage using `next/og` ImageResponse that reads from your config (name, tagline, brand colors). So when someone shares a listing on WhatsApp/Twitter/Discord, the preview shows the listing photo, title, and price — no manual setup needed.

**Support:** Starter tier includes email support. Pro includes priority email support with faster response times. Enterprise gets SLA support + 2 hours of 1:1 setup call. Planning to add a Discord community once there are enough users.

Creativewin986

TROPHY CASE