Do I understand correctly that bleary eyed users were uninstalling the alarm rather than turning it off? (Because by design it's a hassle to turn it off, i.e. to ensure user stays awake for at least some length of time?) That's pretty funny.
My friend (an absolute bear of sleepiness) had a "wifi alarm clock" back in the day: he had to actually stumble over to his router (get a certain wifi signal level) for the alarm to switch off!
I used to have issues walking up during university, leaving my phone on the other side of the room, taking it and turning it off and falling asleep again without memory if it.
I got an alarm app that required solving math questions to do more than snooze. I had set it to three digit numbers +/- another. Worked great. Until I partied a bit too hard, and had to repeatedly snooze it, because even on the bus to university, I was too hungover to figure out the answer ;)
There were not many such apps. Probably I used the same app about 10+ years ago.
And also I was leaving my phone somewhere in the room where I must walk to, so I can actually get out of the bed. On many occasions if someone ring me I can answer and talk to them, assure them that I'm on my way and continue to sleep without even remembering. I listened to recordings, it is funny because I try to change my voice to sound like I am fully awake without even remembering.
Btw, it turns out it was because of my unmanaged t2 diabetes.
Now as it is under control, things are kind of normal.
It can do things like that. People who have diabetes have high blood glucose because their bodies are not actually using the sugar. If it gets bad enough it can actually feel like you're perpetually fasting despite having eaten. The energy is just uselessly circulating in the blood stream. Body thinks it's starving.
If this process continues the body starts producing ketones which acidify the blood which generally causes a lot of symptoms including depression of the nervous system.
A student once made a whimsical motorized alarm clock that could drive around the bedroom, the idea being that the drowsy person would wake up in course of chasing it.
Another student made an alarm clock on the computer, which would require them to be alert enough to solve a differential equation.
> Another student made an alarm clock on the computer, which would require them to be alert enough to solve a differential equation.
That seems like it’d end badly after a rough night. Not only can you not keep sleeping, you can’t function enough to shut off the alarm so you just lie in bed without actually resting. Worst of all worlds. I love it!
When I was in university, I experimented with an alarm app called "sleep as android". I had set it up so I had to scan an NFC tag to turn it off, and for that I used a spent subway ticket I kept in the kitchen.
It worked, until I figured out I could just "force stop" the app lol.
> Do I understand correctly that bleary eyed users were uninstalling the alarm rather than turning it off?
A legitimate reason to do this would be if you're on a red-eye flight somewhere, and your alarm goes off. You can't turn it off because your special object or QR code or whatever is in your checked bag. Your only option is to either turn off your phone or uninstall.
I have been both people in that situation and in both cases we agreed that since the alarm had been set for a reason, a water spray bottle was a perfectly acceptable response once the alarm had been going off for a while.
I also had alarm clock problems in uni. My solution was a Raspberry Pi, a piezoelectric buzzer, and an ultrasonic distance sensor pointed at the bed.
The buzzer would ring until the distance sensor could see the opposite wall, and restart if I went back to bed. As a bonus, it took a few measurements during the night to track sleep quality.
Unfortunately the whole thing was running from a finicky breadboard and needed frequent calibration.
It seems like this could have some awful unintended consequences... e.g. you setup an alarm that can only be deactivated by scanning a QR code in the next room to force yourself out of bed, but forget to disable it on a business trip- and it goes off during an important early morning meeting and cannot be silenced as you aren't home.
I suspect this is almost always not a great solution to this problem. When I was a young adult I used aggressive alarm measures to get out of bed on time, such as having a very loud alarm clock on the far end of the room, where I had to actually get out of bed to silence it.
I discovered realized needing to do this was caused by a number of fixable health/lifestyle issues: going to bed too late, not getting enough daylight and exercise to sync my circadian rhythm correctly, too much screen time and bright lights before bed, too much coffee late in the day, etc. Nowadays I go to bed by ~8pm everyday, fall asleep quickly, and am up early. I haven't needed an alarm even for important very early events in almost a decade.
Is there any malware exploiting this feature? I can imagine "can never be uninstalled" would be a desirable quality.
Especially if the flag doesn't expire, a bad actor could upload a flashlight app with this requirement, let the 20% or whatever tech savvy users balk at the permission, then update later to constantly serve ads or spy or whatever to the remaining 80%, who are now unable to uninstall.
Alternatively, a standard skinner-box inspired mobile game that refuses to uninstall after you've become addicted and traded the ability to uninstall for 500 PremiumBucks or whatever.
I'm legitimately surprised this is a permission that exists outside of the root user
You can always disable screen time permission and uninstall it. Also apps must get a special permission for using this API from Apple, if that’s any consolation.
Never could I have imagined users wanting apps to have more control of them, but here we are with a pretty compelling use case for not letting them remove an app. Neat
I like the idea of apps and components being able to have wide ranges of privileges and those being communicated to the user. I like what the author is doing and everything I don’t like about it - the unfairness of Apple’s gatekeeping and the lack of involvement of the user - is from Apple.
It makes me think of this article I recently read about web components as machines. Perhaps it’s only loosely related, but I feel like it’s worth the tradeoff for the system to create the illusion of components being in charge, even though everything goes through the system, whether it be a web server, a web page, or an operating system. https://www.abeautifulsite.net/posts/component-machines/
What this app attempts to do is to make the alarm be a little bit more like clocky which could do what it did because it was a physical machine. https://en.m.wikipedia.org/wiki/Clocky
Even if you do know the object of the exercise is more "add extra steps" so half awake brain is less likely to manage it without you waking up enough to curse and get up anyway.
Then again, back on my N900 half awake brain once managed to pop a root shell, ps | grep, and kill -9 the alarm clock app without me having any memory of it (the shell was still open when I woke up naturally some time later or I'd never have known what happened).
As stated in the article, that flag is only flipped while the alarm is going off. Also the feature in general is opt-in, and you have to be approved by apple for that feature.
Thanks. Somehow I missed that it is only enabled while the alarm is going off. I did see that it was opt-in and needed approval. But then I was worried about opting in.
but also, like, it only runs in certain conditions it sounds like here.
Can this line of code be always running? What if the app launches itself as a background process?
For a feature I just learned about so many questions, but it's Apple in their store so hedges betting it isn't as dangerous as it sounds. But perks your ears up
By design, apps run in background on iOS only as the system permits. Mostly they don't, except for a limited time in response to notifications, and in some other such sharply circumscribed situations.
I strongly doubt an app asserting this flag would pass review without giving the user a way to opt freely back out in the app's settings.
That goes double for the flag being entitlement-gated, one social reason for which requirement would be that it structurally signals a need for closer review. (I don't have an inside source at Apple, but my experience of their review process prompts the inference.)
The intent is to offer a user the option to strengthen a precommitment, not to offer an app dev the option to permanently infest a device. You can play games in app review, but only up to a point. Trying something like that seems like a good way to get deservedly permabanned.
Granted, I still wouldn't use the app, because I don't need it. But if I did, I'd feel pretty OK about enabling that feature. I might expect it to annoy me enough and aid me so little I'd turn it off again, but I'd see no need whatsoever to worry about being stuck with it.
It's really a matter of perspective. On the one hand, it's creating a situation where a user cannot uninstall the app. On the other hand, it's _allowing_ a user to prevent themselves from being able to uninstall the app under some circumstances. Whether this is ultimately a net increase or decrease in user freedom is an exercise in judgement.
IMO, it's a net decrease, because past owners shouldn't be able to bind future owners. The fact that it's your past self binding your future self, rather than the usual case of the manufacturer binding the end-user, is irrelevant.
But really, this isn't about overruling software, it's about overruling yourself.
Past self has implemented a mandate that future self get up at this time. Future self is a sleepy, lazy, point of sale that can't be trusted.
Sample size of 1. I used to "wake up" and turn off my alarm and have zero recollection of it. I got the most annoying mechanical clock and packed it in a box that I had to unpack before I could turn it off. It got louder as I removed the packaging. The prolonged activity in order to shut off the alarm is ultimately what helped me fully wake up.
People are not always completely lucid immediately upon their alarm clock going off. Have you ever woken up several hours late, only to find that your alarm clock did go off at the scheduled time, but you disabled it and resumed sleeping before fully waking up?
My friend (an absolute bear of sleepiness) had a "wifi alarm clock" back in the day: he had to actually stumble over to his router (get a certain wifi signal level) for the alarm to switch off!
I got an alarm app that required solving math questions to do more than snooze. I had set it to three digit numbers +/- another. Worked great. Until I partied a bit too hard, and had to repeatedly snooze it, because even on the bus to university, I was too hungover to figure out the answer ;)
But in general, I was very grateful for the app.
Diabetes causes sleepwalking? Or mega tiredness?
If this process continues the body starts producing ketones which acidify the blood which generally causes a lot of symptoms including depression of the nervous system.
A student once made a whimsical motorized alarm clock that could drive around the bedroom, the idea being that the drowsy person would wake up in course of chasing it.
Another student made an alarm clock on the computer, which would require them to be alert enough to solve a differential equation.
It’s called “Clocky”: <https://en.wikipedia.org/w/index.php?title=Clocky&oldid=1221...>
That seems like it’d end badly after a rough night. Not only can you not keep sleeping, you can’t function enough to shut off the alarm so you just lie in bed without actually resting. Worst of all worlds. I love it!
It worked, until I figured out I could just "force stop" the app lol.
A legitimate reason to do this would be if you're on a red-eye flight somewhere, and your alarm goes off. You can't turn it off because your special object or QR code or whatever is in your checked bag. Your only option is to either turn off your phone or uninstall.
I was wondering about this, smartphones don't turn on when your alarm goes. (So you could just turn it off to bypass the "super alarm"?)
I have vague memories that older cell phones used to turn on when the alarm would ring, but I might be imagining it.
The buzzer would ring until the distance sensor could see the opposite wall, and restart if I went back to bed. As a bonus, it took a few measurements during the night to track sleep quality.
Unfortunately the whole thing was running from a finicky breadboard and needed frequent calibration.
I suspect this is almost always not a great solution to this problem. When I was a young adult I used aggressive alarm measures to get out of bed on time, such as having a very loud alarm clock on the far end of the room, where I had to actually get out of bed to silence it.
I discovered realized needing to do this was caused by a number of fixable health/lifestyle issues: going to bed too late, not getting enough daylight and exercise to sync my circadian rhythm correctly, too much screen time and bright lights before bed, too much coffee late in the day, etc. Nowadays I go to bed by ~8pm everyday, fall asleep quickly, and am up early. I haven't needed an alarm even for important very early events in almost a decade.
Couldn't you just forcefully turn the phone off? https://support.apple.com/guide/iphone/iph8903c3ee6/ios
Especially if the flag doesn't expire, a bad actor could upload a flashlight app with this requirement, let the 20% or whatever tech savvy users balk at the permission, then update later to constantly serve ads or spy or whatever to the remaining 80%, who are now unable to uninstall.
Alternatively, a standard skinner-box inspired mobile game that refuses to uninstall after you've become addicted and traded the ability to uninstall for 500 PremiumBucks or whatever.
I'm legitimately surprised this is a permission that exists outside of the root user
(Don't know how this works outside of the App Store, which is an interesting question.)
i hope they can dial 911 or hit the link to security cams.
Really effective!
When I didn’t power off the phone.
It makes me think of this article I recently read about web components as machines. Perhaps it’s only loosely related, but I feel like it’s worth the tradeoff for the system to create the illusion of components being in charge, even though everything goes through the system, whether it be a web server, a web page, or an operating system. https://www.abeautifulsite.net/posts/component-machines/
What this app attempts to do is to make the alarm be a little bit more like clocky which could do what it did because it was a physical machine. https://en.m.wikipedia.org/wiki/Clocky
Once you know, it’s easy to do.
Most people don’t know, so this probably does what the author is intending.
Then again, back on my N900 half awake brain once managed to pop a root shell, ps | grep, and kill -9 the alarm clock app without me having any memory of it (the shell was still open when I woke up naturally some time later or I'd never have known what happened).
Surely there is a workaround, right?
> The key is using Screen Time API of iOS.
> After getting approval from the user, the developer can set a flag to deny app removal.
> This feature must be opt-in. To enable the flag, you should explicitly get approval from the user.
Can this line of code be always running? What if the app launches itself as a background process?
For a feature I just learned about so many questions, but it's Apple in their store so hedges betting it isn't as dangerous as it sounds. But perks your ears up
I strongly doubt an app asserting this flag would pass review without giving the user a way to opt freely back out in the app's settings.
That goes double for the flag being entitlement-gated, one social reason for which requirement would be that it structurally signals a need for closer review. (I don't have an inside source at Apple, but my experience of their review process prompts the inference.)
The intent is to offer a user the option to strengthen a precommitment, not to offer an app dev the option to permanently infest a device. You can play games in app review, but only up to a point. Trying something like that seems like a good way to get deservedly permabanned.
Granted, I still wouldn't use the app, because I don't need it. But if I did, I'd feel pretty OK about enabling that feature. I might expect it to annoy me enough and aid me so little I'd turn it off again, but I'd see no need whatsoever to worry about being stuck with it.
v2.5.1
Past self has implemented a mandate that future self get up at this time. Future self is a sleepy, lazy, point of sale that can't be trusted.
Sample size of 1. I used to "wake up" and turn off my alarm and have zero recollection of it. I got the most annoying mechanical clock and packed it in a box that I had to unpack before I could turn it off. It got louder as I removed the packaging. The prolonged activity in order to shut off the alarm is ultimately what helped me fully wake up.
Also, what about force-quitting the app? Couldn't users just do that?
Why would people do that? And why should we prevent this it if that is what they want. I don't understand.