yuriykulikov / alarmclock Goto Github PK

The model concept is not clear yet.

What should alarm do?
What should manager do?

• Tossing ID's around is not nice. Much nicer to toss alarm objects. If alarm is parcel able, there is almost no need for manager in presenters.
• How new alarms should be created?
• How go to bed alarms should be different?
• How much alarms should be aware of each other?
• How to handle persistence? It seems OK how it is handled now.

For this remove the application icon

In the main list use context menu triangles instead of long-click

This button should start a SetAlarmActivity. SetAlarmActivity should add a slider as a second way to set time and show how many hours there are to sleep. As an alternative (for future?), button can replaced with a "drawer handle" to slide in the layout. These are one-shot alarms.

This should be configurable in settings.

Settings entry is required

Checkboxes can be confused with group selection.

Snooze does not work yet, enabling snooze leads to the feedback loop of "Fired - Fire next immediately"

Option - touch an NFC tag to silence the alarm.

Use the light sensor to get screen darker in the bedroom

Add a notification to dismiss snoozed alarms.

Notification with a callback does not look good, because changes to the GUI can be done from an Alarm receiver service. Ok, it is still on the same thread, but from design it is not nice.

Replace pre-alarm checkbox with time selector

Description

Currently pre-alarm can be switched on and off with a single checkbox for each alarm. Replace this checkbox with a time selector (time picker) to make selection more explicit, easier to understand and more flexible, allowing to change pre-alarm durations for each alarm independently.

Success Metrics

Positive user feedback regarding usability

Risks and Assumptions

Requires changes to the database structure

Duplicates

#334

This should be configurable in settings.

Think about optional additional buttons: edit, skip occurence, etc.

Shouldn't, they be light too?

We don't have to update DB everytime something is changed. We have to get data from it on app start and flush it when app ends or major changes happen).

according to http://habrahabr.ru/post/149159/
при свете разрушается гормон сна мелатонин, начинает вырабатываться гормон пробуждения кортизол. Умная лампа включается за полчаса до нужного времени. Но не сразу на полную мощность, а постепенно увеличивая яркость. Одновременно начинают петь птички и шуметь лес – все громче и громче. Плюс, в нужное время зазвучит мелодия.

I find this awesome.

We should not use Theme.Holo.Wallpaper.NoTitleBar to remove KeyGuard. Instead, we should remove it ourselves. This will allow us to have only one AlarmAlert class and no tablet-specific layouts.

This has to be configurable in settings

Currently always vibrates. Should be configurable per alarm and a default setting should be present.

This should be configurable in settings

Snooze notification has to be removed

Add a checkbox into the SetAlarmActivity to make an Alarm a one-shot Alarm. Alarms added this way cannot be enabled or disabled, they can be only removed. They are removed automatically when they fire. This requires GUI, Alarm and DB changes.

This should be configurable in Settings (or not?, please vote)

HW - ASUS Transformer Pad TF300T
Android Ver. - 4.0.3
Kernel Ver. - 2.6.39.4-00003-gafee6c5 android@Mars#1
Build Ver. - IML74K.WW_epad-9.4.3.30-20120604

Actions:
start application
push 'add new alarm'

Issue:
No UI visible result
no option to create new alarm

Merge JB source for translations

Use notifyDataSetChanged instead of clear() and set().

It turns out that for tablets we need something else.
Currently I can come up with:

• Fullscreen interface with desktop background
• Fullscreen interface with analog clock widget
• Fullscreen interface with fragments (like Settings application)
• Dialog interface with buttons

Currently we are using "Dialog interface with buttons". Problem is that there is no access to settings and it does not look very nice. I really think full screen wil look better. What we can do is take a look at other alarms, like doubleTwist alarm.

• Active record container
• or
• saveing strategy

Model:

• Use calendars instead of time in millis to make things more clear and readable
• Move decision making from the Alarm class to a dedicated comparator
• Move Database interaction to a dedicated repository class
• Make Alarm an information expert. Alarm knows better what to do when it is changed.

If alarm has expired while device was off, it will fire the next day.

Alarm should be reverted on destroy or new activity should get its id.

Observed:

• expired was still scheduled
• Snoozed notification does not disable the alarm

Seems that it only affects logs, so low priority.

logger should be able to log everything to the logcat, file, or textview and should be responsible for switching channels on and off. And a way to catch runtime exceptions would be nice as well. This logger can be used to gather info from beta testers in the background (once a day send an email).

HW - ASUS Transformer Pad TF300T
Android Ver. - 4.0.3
Kernel Ver. - 2.6.39.4-00003-gafee6c5 android@Mars#1
Build Ver. - IML74K.WW_epad-9.4.3.30-20120604

Actions:
Start app.

Issue:
'Clock application is stopped' notification
app. not started

This saves two clicks. But we need enough space, so maybe this is only for tablets/phablets. Or use horizontal scrolling or something else.

Snooze alarm did not go and there was no scheduled alarm on the lockscreen afterwards. Snooze notification was still present.

Buttons go to sleep now and go to bed. On the top we can display an icon, settings icon and time to the next alarm. Or vice versa - buttons on top, status on bottom.