rocketsloth

That's an interesting idea. I've added it to the Trello board of ideas I'm considering for recurring alarms and appreciate your suggestion.

Hey sorry for responding so late. Thanks for sharing those libraries, I'll take a look at both. The one i used before was actually quite tough to find and I remember it wasn't a very popular one. I have a release notes list now implemented in the app (as of about an hour ago) and I think i'm going to try the parallax thing soon cause you're really tempting me haha. I really like the idea of experimental settings and think I'm going to do it that way.

If I understand correctly though, I think that suggestion would defeat the purpose of the stroop test that this method is using to trick people, cause the whole idea is that the word ocean is supposed to mislead you and the color of the text can be green. You tap the text color, not the meaning of the word.

Very fair, I picked it cause of all the dismiss methods it's the most visually appealing since the others aren't really based on interacting with the UI much.

I'm working on some alternative palettes right now, and will do my best not to make it worse. One option I'm considering is allowing users to customize the palette entirely by picking 4 colors themselves from a list.

Also while I'm not sure if this is accurate, the android developer mode settings offer the ability to simulate a color space based on various color blindnesses (Monochromacy, Deuteranomaly, Protanomaly, and Tritanomaly) so I'm working with that too.

I only ever tested the parallax library on a very early build of the app which consumed far less ram overall just cause the app wasn't finished yet, so it's hard to give an exact amount. If ever I did any serious animation work and parallax backgrounds I'd leave the option to disable it for users who don't want it or find it impacts performance. I'd also have to do extensive testing with any third party library for parallax cause it's so vital they release sensors properly and without fail when they are no longer needed to conserve battery. I'd love to work on animations in the future cause I think that's one of the areas the app needs the most improvement in and thank you for the complement on the UI.

thanks very much

I'm considering a few options to give more freedom with the alarm (such as repeating and multiple alarms), but I'm working on making sure they integrate with the overall design and concept before jumping the gun.

this may be the best comment of the thread

I've removed the flashing circles in the next build cause I 100% agree and I'd like to clarify that I don't have any intention of pivoting with Nebula cause I really like keeping things simple too. I was just joking around up there :). I think that (at least for me) it feels better to know that you earned something that you couldn't have taken shortcuts on, but I understand your point about how people are ruining things for themselves.

thanks!

Thank you, I didn't notice that. I'll fix that soon

I've looked in to the question and I've changed it so that even the MobileAds SDK is only initialized if premium is not active when the application is first created. This way, if premium is enabled, AdMob is not touched in any way at any stage of the application's lifecycle. I asked whether or not this initialize call I was worried about actually does anything with respect to tracking and the only answer I've gotten so far is a "no", but I still need to do a little more research to make sure there aren't any other possible ways you may be tracked if ads aren't ever being loaded or requested. This additional check will go live in a day or two and I'll update you if I find any other potential issues.

I agree that sleep is a complicated thing and that bedtime routines are vital to overall healthy sleep habits. I think you're right and that reinforcing good sleep scheduling is the next step with the app in terms of big features

I've heard really great things about them