James Fenn

Hmm, interesting idea. Honestly, the way that Alarmio stores & retrieves alarm data could perhaps use a few improvements, so I'll keep this in mind as a potential feature once...

@kentone sorry for the late reply. Normally it might be a good idea, but it doesn't make a huge difference either way - it's a simple fix \:)

Assuming I've understood this correctly, the most UX-friendly way to implement this would probably be to treat them as "bookmarks" - maybe keeping track of the durations most frequently used...

@ajayyy No worries! I think this is more of a problem with a lack of documentation / readability than a definitive bug... converting to Kotlin should make it more clear...

Is an explicit "home" time zone necessary? This could just involve filtering out time zones equivalent to the current location from the list - the first page will always be...

Alarmio currently relies entirely on the Android system to implement time zones, daylight savings, etc - I'm not sure if there's an easy way to change its behavior without involving...

Valid suggestion - this could be implemented along with the "sleep reminder" feature, which I believe currently has some compatibility issues on newer Android versions (#43) and will need to...

My immediate suspicion goes to Android 8+ background restrictions - Alarmio should already do this on prior Android versions (unless it doesn't, in which case, err, ignore me). If so,...

Err, that's odd. IIRC the only thing it should use the network for is fetching items in the about screen. Do you know what server/URL it's connecting to?

Oh, I forgot about the header image - Alarmio's default background is fetched from my website to prevent it from pointlessly inflating the APK size. You can change this behavior...