maza

@simonecanciello People will rather go broke than skip socials

a $1M app idea: pay cents every time you want to open distracting apps.

@solodev_ship MRR*

@solodev_ship I mean if you have a iphone (i assume) you can test it realtime with the expo go app. For building and submitting it you don't really need a mac, expo handles everything in cloud. But anyway the crazy part is the 30k MMR, not that you do it on a window. what kind of app is that?

I just crossed $31,000 MRR in 6 months as a solo dev. The craziest part? I launched and scaled an iOS app without even owning a Mac. Here is how I completely bypassed the "Apple Tax" and kept my startup incredibly lean: 👇 #buildinpublic

@spuyet nice, I was looking for something like this since I self host. will definitely try it

GPU monitoring just shipped on fivenines.io 🔥 NVIDIA GPUs auto-detected, full metrics: → Utilization & memory → Temperature, power, fan speed → Per-process GPU usage Update your agent, enable the feature and it just works. #buildinpublic #linux #monitoring #gpu

@denizay_js congrats man! what channel did you use to get there?

Just hit 10,000 downloads in 3 months — solo, no team, no funding 🚀 Built it, shipped it, marketed it. All by myself. 10K is just the beginning. The goal is 100K 🎯 If you're a solo dev sitting on an idea — just start. The market will tell you the rest. 💪 #buildinpublic #indiehackers #startupjourney

@ModestMitkus been thinking about hooking it to sentry for error monitoring and open PRs to github to fix them. But tbh looks like a real pain to set it up

Genuinely curious, for what purpose you use OpenClaw? I personally tried it but don’t really see how much it can improve anything to me to be honest. It has all the tools and access but still gets tracked and restricted as bot even from simple web search.

@shazcodes Look Next is great but yeah for small apps is simply too much. NextJS is a full-stack framework and people tend to forget it. They choose it to build landing pages and todo apps just because it’s the most “popular”. That’s the real problem, not the framework itself.

i’m convinced Next.js is just a massive social experiment to see how much complexity developers will accept for a “hello world” app.🤡 i have 100 reasons to hate it, but let’s start with the big ones: - file-based routing is a nightmare for anything larger than a todo list. - the app router is still fundamentally unstable and makes the developer experience (DX) feel like a sluggish beta. - cold starts and build times are becoming a joke, waiting minutes for a simple deployment isn't fast. - middleware Limitations make basic tasks like authentication and headers unnecessarily difficult compared to a standard express/node setup. Why are we still pretending this is progress? back to vite/remix we go.

@justbyte_ Go with Next. You'll still learn all the important React stuff while actually shipping something. The difference is Next handles the setup stuff behind the scenes. You're building, not configuring.

Be honest, which one is beginner friendly??

96% stat is wild but not surprising. The reason most skip it is not that they don't care. it's that the setup is never actually "30 seconds". You run the wizard, then you're configuring source maps, wrapping your config, adding providers, and then you open the dashboard and it's 15 tabs of breadcrumbs and traces just to find what actually broke. Error tracking needs to be boring simple or nobody bothers

I scanned 45 product hunt landing pages and found 96% have ZERO error tracking. That means when your site breaks, users just... leave. Add Sentry in 30 seconds: npx @sentry/wizard@latest -i nextjs You'll catch errors before users abandon your site.

@mayer_gall @paciosdev I bet it identifies eye color

@paciosdev what does the app exactly do ?

@dannypostma Is like the hero itself is an ad space. Genius.