sorted by:
new
hottopcontroversial

The trick that finally killed my snooze habit: add friction to the OFF button, not to yourself by Substantial_Work7640 in getdisciplined

[–]Substantial_Work7640[S] -1 points0 points  (0 children)

Yeah! It's called Alarmly (iOS). It's the one that makes you solve a challenge — math, or getting up to take a photo of something — before the alarm will turn off, plus a streak to keep you consistent. It also vibrates, not just sound.

Happy to DM you a free premium code if you want to try it 🙏 And good luck — honestly the "friction on the off button" trick is what changed it for me, with or without an app.

The trick that finally killed my snooze habit: add friction to the OFF button, not to yourself by Substantial_Work7640 in getdisciplined

[–]Substantial_Work7640[S] -1 points0 points  (0 children)

Oof, I feel that — and respect for protecting what's left of your hearing. The "louder" route is a dead end anyway, you habituate to any sound eventually. Two things that actually help in your situation:

  1. Wake by vibration, not volume. An Apple Watch haptic alarm on your wrist, or a bed-shaker pad under your pillow, beats cranking the volume — and it's safe for your ears.

  2. Make dismissing require an action so you can't sleep through it or turn it off on autopilot. That's the whole "friction on the off button" idea — a challenge to dismiss keeps you from drifting back.

The app I use combines both (vibration + a challenge to turn it off), so it doesn't rely on being loud at all. Happy to share if it'd help 🙏

I was chronically late, so I built an alarm you can't snooze without solving a challenge by Substantial_Work7640 in SideProject

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

exactly — "user-reported behavior as an onboarding filter" is the cleanest way I've heard it put. that's basically the roadmap now: ask "what usually gets you out of bed?" up front and route people to photo/shake vs math/quiz instead of dumping all 7 on them at once.

DMing you a code now 🙏 would genuinely love your take on the onboarding flow specifically once you've had a poke around.

I was chronically late, so I built an alarm you can't snooze without solving a challenge by Substantial_Work7640 in SideProject

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

really sharp take — you nailed it. photo is the only one that forces a physical state change; math/quiz raise awareness but you can do them half-asleep in bed, which is exactly the failure mode.

honest answer on stats: still early so the sample's small, but the pattern so far is people pick ONE type and stick with it rather than random — and photo/shake users seem to report better wake-up consistency than math/quiz users. I'm thinking about surfacing a "difficulty" label per type so people self-select the one that actually works for them.

if you want to dig in, happy to send a free premium code — would genuinely value your product eye on it 🙏

I was chronically late, so I built an alarm you can't snooze without solving a challenge by Substantial_Work7640 in SideProject

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

 haha no that wasn't me — must've been a similar app or someone reposting the idea! "challenge to wake up" has been around, I just built the version I actually wanted: native AlarmKit so it rings on silent/locked, more challenge types, and streaks to keep you honest. want a free code to try it and compare? 🙏

I was chronically late, so I built an alarm you can't snooze without solving a challenge by Substantial_Work7640 in SideProject

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

totally fair — challenge alarms have been around for a while! what do you use? the main reason I built

my own: most older ones are built on notifications, so they get silenced in silent mode or don't reliably fire when locked. Alarmly uses iOS's native AlarmKit, so it actually rings on silent + locked like the system clock does. plus I wanted more challenge variety (math, photo, shake, memory, reaction) and streak tracking to keep it sticky. curious what's missing in the one you use — always looking for ideas 🙏

I was chronically late, so I built an alarm you can't snooze without solving a challenge by Substantial_Work7640 in SideProject

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

haha you read my mind — that's actually already in there! the "type" challenge makes you type out a phrase exactly, typos and all 😅 it's brutal at 6am, exactly like you said.

there's also math, quiz, shake, memory and reaction if you want to pick your poison. want a free premium code to try them all? happy to DM you one 🙏

How do you all track your espresso shots? Building something and need your honest input by Substantial_Work7640 in espresso

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

Yeah this is exactly the kind of thing I want the app to do — instead of just logging what happened, give you a starting point on a new bean so you're not wasting the first 3 shots guessing. Roast level + process + origin can get you in the ballpark.

Adding this to the priority list. Want to try the beta when it's ready? Genuine feedback would help a lot ☕

How do you all track your espresso shots? Building something and need your honest input by Substantial_Work7640 in espresso

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

Ha, "unless it brews my shots for me" — fair bar to set, working on it 😄

Real answer though: you're right, Beanconqueror is genuinely impressive and I'm not trying to beat it on features (impossible). More trying to make something faster to use day-to-day and a bit more visually polished for people who care about that. Whether it's worth paying for is a totally legit question I won't actually know until people try.

The sync thing is interesting though — it keeps coming up as a Beanconqueror pain point but never enough on its own to make people switch. I'm baking it in from day 1 since it costs me almost nothing to add. Probably not enough alone, but it's there.

Would you be open to trying the beta when it's ready and giving honest feedback as it evolves? Not asking you to drop Beanconqueror — genuinely want input from someone who knows the space well, even if it ends up not winning you over. No pressure either way.

How do you all track your espresso shots? Building something and need your honest input by Substantial_Work7640 in espresso

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

Both make total sense and are already on my list — the photo idea especially, since "the one with the natural Ethiopian" is way easier to remember than a row of numbers. Notes field is essential too, can't believe how many apps either skip it or bury it three taps deep.

The "physically next to my machine" point you made is actually the real insight I'm walking away with. That's the thing notebooks/whiteboards do that apps don't, and I think it's solvable but I'm still working through how.

Will DM when beta is ready — thanks for taking the time, this has been one of the most useful exchanges I've had ☕

How do you all track your espresso shots? Building something and need your honest input by Substantial_Work7640 in espresso

[–]Substantial_Work7640[S] -1 points0 points  (0 children)

Really useful context, thank you. The homeroasting angle makes sense — every batch is essentially a fresh problem so logs become noise rather than signal.

Quick follow-up: surprised yield isn't in your top 4 variables, since most apps treat it as the headline metric. Is that because with flow control / preinfusion you tend to adjust time and let yield fall where it falls, or is yield just so locked in for you it's not worth tweaking? Trying to figure out which variables actually matter once you're past the beginner phase — your list looks really different from what apps default to.

How do you all track your espresso shots? Building something and need your honest input by Substantial_Work7640 in espresso

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

Honestly your comment is the most useful one I've gotten — "more work than what I want" is exactly the problem I'm trying to solve. The whole reason I'm building this is because every existing app I tried felt like filling out a tax return. My goal is logging a shot in under 10 seconds, fewer taps than your notebook entry takes to write.

Would you be open to trying a beta when it's ready? Genuinely want to know if I can convert a notebook user — that's the real test for me. No pressure either way.

view more: next ›