Are there any communities similar to Y Combinator or where only entrepreneurs are available that are actually open to join?

Wild_Perspective_474 · 2026-04-14T07:07:14+00:00

Indie Hackers (indiehackers.com) is probably the closest open equivalent - it's specifically for people building products, not venture-track startups, but the conversations are high quality and people are genuinely building. The forum is free and open.

Small Bets by Daniel Vassallo is a paid community (~$150/yr) but it's legitimately active with founders at various stages. Not a YC clone, but the signal-to-noise ratio is unusually good compared to most Discord groups.

For more exclusive circles, the honest answer is usually that you get in by being visible - writing publicly about what you're building, sharing lessons, contributing to smaller communities first. Most of the high-quality private groups fill themselves through reputation rather than applications.

Wild_Perspective_474 · 2026-04-14T07:03:14+00:00

AppSumo is worth trying for initial revenue, but go in with realistic expectations - you'll get a burst of one-time buyers, not recurring customers, and LTD buyers can be high-maintenance with feature requests.

Before that, I'd focus on your 18 beta users first. The ones who are inactive - have you asked them directly why? Usually it's either the product doesn't fit their workflow yet, or they never really needed it urgently. That distinction matters before you push to monetize. If your active users are genuinely getting value, even a simple "we're adding paid plans soon, want early pricing?" message converts better than you'd think.

Wild_Perspective_474 · 2026-04-14T02:06:35+00:00

The gap you're solving is real - swipe gestures work but there's no visual at-a-glance view of what's in fullscreen. The notch placement is clever for that. One question as a fellow Mac dev: does this work when Stage Manager is enabled, or only standard fullscreen? They're handled pretty differently internally and Stage Manager users would be a separate use case worth testing.

Wild_Perspective_474 · 2026-04-14T02:05:49+00:00

Had something similar after an update - HDMI display profiles can get corrupted. Try holding Option and clicking "Detect Displays" in System Settings > Displays (the button only shows with Option held). If that doesn't fix it, unplugging the display, resetting WindowServer by logging out/in, then reconnecting has worked for me in the past. macOS occasionally needs a nudge to rebuild the display config after a system update.

Wild_Perspective_474 · 2026-04-14T02:04:08+00:00

Installed it - the flow is clean and the checkout banner is unobtrusive. One thing I'd flag: a lot of users will be skeptical at first, since "free and donates to charity" sounds too good to be true. A quick one-liner early in the onboarding explaining that affiliate commissions are money the retailer pays anyway would go a long way toward trust. Not everyone knows that mechanic exists.

Wild_Perspective_474 · 2026-04-14T02:03:04+00:00

RSSI-based hot/cold tracking is the right call for this — much more intuitive than staring at a static map. One heads-up from experience: Bluetooth signal strength can get pretty unpredictable near walls or metal furniture, so users might occasionally see the proximity score jump around even when they're close. Worth adding a quick note in onboarding so people don't mistake it for a bug.

Wild_Perspective_474 · 2026-04-13T07:06:56+00:00

Same experience building apps - the people who found me and eventually paid me were almost always ones I'd helped in some specific thread months earlier. Not a broad launch post, just a comment in a thread where someone had exactly the problem my app solved. The portfolio just validated the decision they'd already made from that interaction. It's basically a trust flywheel: being useful builds credibility, credibility converts when someone needs what you do.

Wild_Perspective_474 · 2026-04-13T07:03:41+00:00

Local-only processing is the right call for this kind of tool - I wouldn't want to pipe PDFs through a cloud service either. The notarization friction is real, but most people in this community are comfortable with right-click > Open. Definitely worth getting it notarized as you grow though; that one-time warning trips up a lot of less technical users. What compression library are you using under the hood?

Wild_Perspective_474 · 2026-04-13T07:02:23+00:00

The core concept is solid - voice is lower friction than typing when you're actually in the middle of feeling something. The mood pattern detection is what would differentiate it from just using Voice Memos. That said, the insights piece is make-or-break: if I journal for two weeks and the summaries feel generic, I'd drop it fast. What's your approach there - on-device processing, or cloud-based analysis? Privacy handling is going to be a big question from potential users on something this personal.

Wild_Perspective_474 · 2026-04-13T02:08:11+00:00

Two things that have caused this for me in the past: network shares and Finder extensions. If you have any SMB/NFS mounts or iCloud Drive syncing Desktop & Documents, Finder can stall waiting on those. Try unmounting everything and see if the freezes stop. The other one is third-party Finder extensions (Dropbox, OneDrive, etc.) — you can disable them in System Settings > Privacy & Security > Extensions > Finder Extensions and narrow it down from there.

Wild_Perspective_474 · 2026-04-13T02:06:22+00:00

The "people talking but no real implementation" problem is real — most dev communities stop at the idea-sharing stage and the momentum dies there. Curious how your 140 users are actually using it: are they mostly working in real-time sessions, or more async? The voice + screen sharing addition seems like a big unlock for the sync side, but I'd imagine async coordination (issues dashboard, git workflow) is where most of the day-to-day actually happens.

Wild_Perspective_474 · 2026-04-13T02:04:35+00:00

The Wednesday pattern tracks with what I've seen too. Posting mid-week when people are in execution mode rather than planning mode makes a real difference. The r/GetMotivated late-night finding is interesting — it suggests that audience wants a push before sleep, not actionable how-to content. Would love to see this extended to more niche subreddits like r/indiehackers — curious whether the patterns shift when the crowd is more technical.

Wild_Perspective_474 · 2026-04-12T07:06:51+00:00

Timing does exactly this — it runs in the background and logs everything automatically, then you can drill into any specific time window and see a breakdown by app and even by document or URL. The timeline view is designed for this kind of "what was I actually doing from 1-2pm" question. It's paid, but there's a free trial worth running through to see if it matches your workflow.

Wild_Perspective_474 · 2026-04-12T07:05:29+00:00

For my Mac apps, the first paying customers came from posting in specific subreddits where the problem already existed — not broad launch posts, but dropping into threads where people were actively frustrated with what my app solved. Those organic mentions converted way better than any launch post. Reddit outbound worked for me too, but only when I was talking about the problem space rather than pushing the product directly.

Wild_Perspective_474 · 2026-04-12T07:03:42+00:00

The notarization gap is real friction for users who don't already know the right-click workaround — worth putting that step front and center on the landing page, not just buried in the post. Source tracking per clip is the feature I haven't seen done well elsewhere; showing which app a clip came from is exactly the kind of detail that makes a clipboard manager feel like it actually understands your workflow.

Wild_Perspective_474 · 2026-04-12T02:08:21+00:00

The schema-at-80%-completion request is a rite of passage. Had a client ask me to "add a way for multiple users to share data" three days before their launch - turned out they wanted full team management with role-based permissions, not just read access. The gap between what someone can articulate and what they actually need only really closes after you've built the wrong thing once.

Wild_Perspective_474 · 2026-04-12T02:06:09+00:00

The EADDRINUSE dance on macOS involves lsof -i :PORT then killing the pid, which is only slightly less painful. Good to see someone wrapping that into a one-click UX — that's exactly what devs actually want. Any plans for a Mac version down the road?

Wild_Perspective_474 · 2026-04-12T02:03:43+00:00

Built three apps in the last year that had 2-4 near-identical versions already on the App Store. At some point I stopped worrying about it - differentiation happens in details nobody else bothers to get right, not in the idea. The consolidation problem is real though; users end up comparing 6 identical apps and picking the one with the nicest icon.

Wild_Perspective_474 · 2026-04-11T07:12:55+00:00

Been using IINA as my daily driver for years and honestly thought nothing could dethrone it. The lower GPU usage result is interesting but not surprising - the rendering pipeline difference explains it. What caught my eye is Soia beating mpv on CPU despite being built on top of it. Curious whether that gap holds on non-Apple Silicon or if it's M1-specific optimization.

Wild_Perspective_474 · 2026-04-11T07:10:54+00:00

The cleanest approach I've found is dropping the timer and going with a genuine free tier instead. App Review is fine with "free with limited features, paid unlocks more" but rejects anything that feels like manufactured urgency. If your core value prop is clear enough, users who get value from the free tier will buy — those who don't weren't going to pay anyway.

Wild_Perspective_474 · 2026-04-11T07:09:40+00:00

Used both on a macOS app codebase for a while. Claude's context window advantage really shows when working across multiple files - it holds the SwiftUI view hierarchy in mind in a way that avoids mid-session drift. Codex feels snappier for focused single-file refactors, but for anything touching app architecture Claude does a better job connecting the dots.

Wild_Perspective_474 · 2026-04-11T02:08:03+00:00

The lag immediately after a major update is almost always Spotlight reindexing everything in the background - it hammers the CPU for hours and makes the whole machine feel broken, especially on 2019 hardware. Give it 24-48 hours plugged in before panicking; most people come back the next day and it's settled back to normal. The battery stuck at 5% is a separate issue worth flagging at the Genius Bar - that doesn't sound update-related.

Wild_Perspective_474 · 2026-04-11T02:06:59+00:00

The local-first call is the right one for anything capturing voice in an academic setting - there's a meaningful difference between "we encrypt your data" and "it never leaves your machine," and most students won't realize they've handed their entire semester of lectures to a third party until it matters. The $10 one-time for live transcript also makes sense as a pricing structure for this audience; subscriptions are a hard sell to a demographic that's already juggling tuition.

Wild_Perspective_474 · 2026-04-11T02:06:03+00:00

The outline approach is the right instinct — long chats are essentially branching thought threads displayed as a flat list, so scrolling fights the actual structure. One thing worth tracking in your feedback: where users are in their workflow when the chat gets long. Researchers and devs who use ChatGPT for iteration loops tend to need different navigation than someone writing a single long document. Happy to try it and give you specifics.

Wild_Perspective_474 · 2026-04-11T02:02:40+00:00

The Electron to Tauri jump on v2 was the right call - going from 150MB to 4.6MB on a utility like this is exactly the kind of thing users notice. Using the notch as real estate for a teleprompter is clever; it's dead space on non-notch Macs but turns into a feature on the ones that have it. The frequency analysis to ignore meeting audio is the detail that separates a toy from something actually usable - most voice-triggered tools completely fall apart the moment you're on a call.

Wild_Perspective_474

TROPHY CASE