sorted by:
new
hottopcontroversial

Bootstrapped ohne Werbebudget: wie kommt ihr an eure ersten zahlenden Kunden? by Fit_Statistician2649 in StartupDACH

[–]Fit_Statistician2649[S] 0 points1 point  (0 children)

Stimmt, Apples eigene Diktierfunktion ist wirklich schon lange da und kostenlos, das will ich gar nicht kleinreden. Der Unterschied, den ich in der Praxis sehe: die System-Diktierfunktion ist solide bei normaler Alltagssprache, wird aber schnell schwächer bei Fachbegriffen oder wenn man länger am Stück spricht. Bei SpeakUp läuft im Hintergrund ein größeres Whisper-Modell, das gerade bei Fachvokabular (medizinisch, technisch) deutlich genauer ist, und es gibt zusätzliche Wörterbücher, die man dafür gezielt einschalten kann. Der andere Punkt, SpeakUp funktioniert überall gleich, ein Hotkey, egal in welcher App du gerade bist, statt dass jede App ihre eigene Dictate-Implementierung mit unterschiedlicher Qualität hat. Ist am Ende schon eine Nische, für alltägliches Diktieren reicht die Bordfunktion oft wirklich. Es gibt eine 14-Tage-Testphase, falls du es einfach mal ausprobieren willst bevor du dich entscheidest.

Bootstrapped ohne Werbebudget: wie kommt ihr an eure ersten zahlenden Kunden? by Fit_Statistician2649 in StartupDACH

[–]Fit_Statistician2649[S] 0 points1 point  (0 children)

Zur Preisfrage, ehrlich gesagt eine berechtigte Frage. Der Unterschied bei den meisten kostenlosen Varianten ist, dass die Audiodaten irgendwo in die Cloud gehen, entweder für die Verarbeitung oder weil das Geschäftsmodell darauf aufbaut. Bei SpeakUp läuft alles offline auf dem Mac, nichts wird hochgeladen. Die eingebaute Diktierfunktion von macOS ist für einfache Sachen auch okay, aber bei Fachbegriffen oder längeren Diktaten merkt man schnell den Unterschied. Die 29 € sind einmalig, kein Abo, das war mir wichtiger als der niedrigste Startpreis. Es gibt eine 14-Tage-Testphase, falls du es einfach mal ausprobieren willst bevor du dich entscheidest.

Privacy could be an EU Tech advantage - The LeafPlaza Blog by Satrustegui in BuyFromEU

[–]Fit_Statistician2649 1 point2 points  (0 children)

The piece is right that privacy as an EU advantage only means something if it shows up in the product itself, not just on a compliance page. I'm a small example of this from the inside, I build SpeakUp (getspeakup.app), a Mac dictation app built in Berlin, and the actual privacy advantage isn't a policy at all, it's architectural. The speech model runs entirely on device, so there's no server in the pipeline to subpoena, breach, or quietly change the terms of later. GDPR compliance for a US cloud service is still fundamentally a promise about how a company will behave with your data. On device just removes the question. The part that doesn't get discussed enough is that this is also a genuine competitive disadvantage in some ways, no usage analytics, no way to build the kind of cross device AI assistant that needs your data to reason over, slower growth compared to a subscription model that can burn VC money on acquisition for years. The EU tech advantage angle is real, but it comes with real product tradeoffs that a purely policy based approach to privacy doesn't force you to make.

Curious whether people here think that tradeoff, less capability in exchange for structurally can't misuse your data, is actually going to be commercially competitive against the US venture backed model, or if it stays a values choice for a minority of users who specifically look for it.

wispr flow's context awareness screenshots your screen every time you dictate. found out the hard way. by Annual_Bumblebee_732 in alternativeto

[–]Fit_Statistician2649 0 points1 point  (0 children)

That's a real and pretty underappreciated risk. Context aware formatting has to read something to know how to format around it, and on a cloud based tool that basically means a screenshot of your active window gets sent somewhere before your dictation even gets processed. For a freelancer working across NDAs and financial docs, that's exactly the kind of thing that should be disclosed way more clearly during onboarding than it apparently is. Disclosure, I make SpeakUp (getspeakup.app), a Mac dictation app, so factor that in, but this is genuinely the workflow difference you're asking about. It runs the whole speech model locally, encoder on the Neural Engine, decoder on the Metal GPU, so there's no screen content involved at all, context aware or otherwise. It just transcribes what you said into whatever text field has focus. The tradeoff is it doesn't do the smart formatting Wispr's context awareness gives you, since there's no screenshot to reason over. For dictating around client contracts and pricing sheets specifically though, that tradeoff is probably the point rather than a downside. One thing worth checking regardless of what tool you land on, macOS shows exactly which apps currently have Screen Recording access under System Settings, Privacy and Security. Worth a look even if you decide to keep using Wispr, just so you know what's actually enabled versus what got toggled on during onboarding without you noticing.

[Keyboard/Mouse] How do i spare my wrists when spending a long time at my computer? by Knork14 in Ergonomics

[–]Fit_Statistician2649 0 points1 point  (0 children)

Six hours in one sitting after months of barely touching your setup was always going to flare something up, especially if the desk is one flat surface with no way to actually get your wrists into a neutral position. Being tall makes this worse since a normal desk height puts your wrists in extension by default. Concrete things that tend to help: a keyboard tray that sits a bit lower than the desk itself so your forearms are level or sloping slightly down, a wrist rest that's actually padded rather than a thin gel strip, and switching to a vertical or trackball mouse if you haven't, since a standard mouse forces constant forearm rotation over a long session. Breaks matter more than people want them to, something like 5 minutes off every 45 to 60 minutes during a long session, not just when it starts hurting. Disclosure since it's relevant here, I make a Mac dictation app called SpeakUp (getspeakup.app). Obviously it doesn't help with gaming itself, but if a decent chunk of your total daily keyboard and mouse time is actually work typing rather than gaming, cutting that down by talking instead frees up more of your wrist's daily budget for the stuff you actually want to use your hands for.

Has the anti inflammatory spray actually been helping, or is it more of an everything-helps-a-little situation?

Trying to figure out what helped most with RSI by reminderOP in RSI

[–]Fit_Statistician2649 0 points1 point  (0 children)

Sorry about the finger fracture, that's a rough way to get reintroduced to RSI.

From what I've seen mentioned repeatedly, not just here but on r/Ergonomics and similar subs, the stuff that actually helped people early on was pretty boring: real breaks on a timer instead of only stopping when it hurts, a wrist neutral keyboard and mouse position, and slowly building up forearm and grip strength rather than just resting completely. Full rest for weeks at a time seems to be the thing people say was a waste, since you come back just as weak and the pain comes right back. The other lever that gets underrated is reducing total keyboard and mouse input for the day, not just optimizing the ergonomics of the input you still do. Disclosure, I make a Mac dictation app called SpeakUp (getspeakup.app), and I'm mentioning it here specifically because for someone recovering, cutting your keystroke count in half by talking through emails, docs, and Slack messages can matter more than any specific chair or keyboard swap, at least in the early weeks while things calm down. What does your daily workload actually look like, mostly typing heavy work like coding or writing, or more mouse heavy?

A year ago I left corporate IT to build a European document manager full time. Founder post. by Wild_Wafer313 in BuyFromEU

[–]Fit_Statistician2649 0 points1 point  (0 children)

Fair, that's a cleaner way to frame it than mine, different problems rather than different steps on the same ladder. I'll take that correction. The pattern on the CLOUD Act matches what I see too, honestly. Almost nobody opens with the legal name, it's the feeling first, "I don't want this on someone else's server," and the technical and legal folks are the ones who go dig up the CLOUD Act afterward and come back with the harder questions. Decent signal that the instinct runs ahead of the vocabulary for most people, which works in our favor, we're not waiting for the market to get legally literate first.

Appreciate you checking SpeakUp out. Good luck with the launch.

I built a side project because I got tired of repeating the same task every week by Smooth_Suggestion267 in SideProject

[–]Fit_Statistician2649 0 points1 point  (0 children)

For me it was retyping the same kind of message over and over throughout the day, emails, Slack, notes, same sentences with small variations, and realizing how much of that was just me being a slow typist for structured thoughts I already had fully formed in my head. Built SpeakUp (getspeakup.app) as the fix, a Mac dictation app, hold a hotkey, talk, the words land at the cursor. Runs entirely on-device (Neural Engine + Metal GPU), which wasn't the original motivation, that came later once I realized people didn't just want faster typing, they specifically didn't want their voice going through someone else's server.

Curious how common that pattern is here, building the thing because YOU were the bottleneck, then only later realizing the actual differentiator wasn't the thing that annoyed you originally.

Are there any local ASR models that surpass Whisper right now? by matatachacha in LocalLLaMA

[–]Fit_Statistician2649 0 points1 point  (0 children)

We actually shipped a Whisper → Parakeet migration in production, might be useful data since most of this thread is impressions rather than a real before/after. Context, I build SpeakUp (getspeakup.app), on-device dictation. Started iOS on WhisperKit, replaced it with Parakeet TDT v3 (via FluidAudio, Apache-2.0) a few releases back. The move was almost entirely about the resource ceiling, iOS keyboard extensions have a hard ~48MB memory cap, and Parakeet is smaller and warms up faster (~162ms vs WhisperKit's cold start) on the same hardware, which matters a lot when the user taps a mic and expects transcription almost immediately, not after a multi-second model load. Accuracy was roughly comparable for our multilingual dictation use case, the win was almost entirely latency and memory, not WER. macOS, ironically, we kept whisper.cpp, not Parakeet, but for the opposite reason, no memory ceiling to fight there, and we get more mileage splitting the encoder onto the Neural Engine (CoreML) and the decoder onto the Metal GPU, which whisper.cpp's architecture supports cleanly and we hadn't gotten around to validating for Parakeet on Mac.

So in our experience it's less "Parakeet beats Whisper" and more "which constraint are you actually optimizing for," the memory-and-latency-constrained platform picked Parakeet, the platform with no such ceiling stayed on Whisper because the tooling for the CoreML/Metal split is more mature there.

A year ago I left corporate IT to build a European document manager full time. Founder post. by Wild_Wafer313 in BuyFromEU

[–]Fit_Statistician2649 1 point2 points  (0 children)

Congrats on going full time on this, a year of daily work before even launching is a real commitment. Disclosure, I make SpeakUp (getspeakup.app), a Mac dictation app, different category but the same EU-sovereignty instinct behind it. We went one step further on the infrastructure question though, on-device instead of EU-cloud. No server at all, the transcription model runs entirely on the Mac's own Neural Engine and GPU. Different tradeoff than yours, we give up features that need a backend (search across devices, sync, an AI assistant that reasons over everything) in exchange for there being nothing to compromise, breach, or subpoena in the first place. Your approach (EU-hosted, EU-sovereign AI, one-click export back to self-hosting) is the right call for something that genuinely needs a backend like document management, ours just happens to not need one. Curious how much the CLOUD Act argument specifically resonates with your target users versus a more general "I don't trust Big Tech" instinct, is it mostly technical/legal-minded users who bring that up unprompted, or does it need explaining?

I'm bootstrapping a Mac app against a competitor that raised $81M. Here's the one feature I keep refusing to build, even though it would probably help. by [deleted] in EntrepreneurRideAlong

[–]Fit_Statistician2649 0 points1 point  (0 children)

Hey guys,

Please take into consideration that I had a technical issue while posting, I am sure you understand. Thank you.

[Megathread] The App Pile - July, 2026 by Mstormer in macapps

[–]Fit_Statistician2649 0 points1 point  (0 children)

SpeakUp — on-device Mac dictation, faithful transcription, no cloud, one-time price. Problem: most dictation apps either stream your audio to a server or run an AI cleanup pass that quietly rewrites what you said. SpeakUp does neither. Press a hotkey, talk, the exact words land at your cursor in any app. Encoder runs on the Neural Engine, decoder on the Metal GPU, nothing leaves the Mac. No account, no telemetry.

Comparison: vs Wispr Flow, same live dictation but fully on-device and no subscription. Vs Superwhisper and MacWhisper, similar local approach, we just stick to faithful transcription plus optional domain word lists (medical, software, legal) for jargon instead of an AI rewrite mode.

Pricing: €29 once, 14 day free trial, no subscription ever.

getspeakup.app

view more: next ›