igilham / ios-pomodoro Goto Github PK

Each day's task list should be persisted with the date to enable historical analysis.

The amount of history should be restricted to some time period ( 1 month? 1 year?)

After interrupting a timer, the user will be asked if they want to abandon the work period or resume from where they left off after dealing with the interruption.

For each abandoned work period, increment a counter of abandoned periods for the task in the model.

The OS may blank the screen and/or otherwise put the app to sleep. The timer should continue to work in that scenario and raise a notification when finished.

Use a calendar or similar to select historical days of data and display their task list.

A basic visual representation of a timer with a task label and a single button to stop and abandon the work period.

Stopping the timer navigates to the task screen.

Completing the timer records a completed timer against the task and displays a completion message. This changes the button to just return to the task screen without affecting state.

For every interruption, increment a counter of interruptions against the task in the model.

• add setting for number of days to calculate statistics over
• display average number of tasks per day
• display average number of estimated work periods
• display average number of completed work periods
• display average number of interruptions
• display average number of abandoned work periods

Display the count of interrupts and abandoned work periods in the main task list user interface.

Make historical task views read-only to prevent editing.

The pomodoro timer screen should allow the user to start a break timer after each completed work timer. The typical duration of a break timer in the Pomodoro Technique is 5 minutes.

• after completing a work timer, the acknowledgement button starts a break timer (default: 5 min)
• the break timer can be dismissed with a button
• the break timer has a different visual representation

Providing a view to enable users to alter the lengths of timers would allow the application to work more flexibly for people with varying requirements.

Create a new screen for surfacing user settings

• work timer duration (25min)
• break timer duration (5 min)
• long break timer duration (30min)

The input control used to create new tasks is not very user-friendly. The application currently uses an Alert control, which exposes two unlabelled text boxes. The user must write a string into the first box and an integer into the second for the task to be created successfully. A better design would be to implement a new input screen with some help text and labelled input controls, including a more suitable numeric input for the task estimate.

There is not currently any way to edit a task’s title or estimate once it has been created. The screen used to create new tasks (as described in #17) could be further used to edit the details of an existing task. It may also be useful to be able to mark the task as done from this screen.

The created tasks and state for the day should be persisted in case the app is closed.

The state should be loaded on startup if it exists.

First app screen, showing a list of tasks.

User features:

• add a task
• remove a task
• edit a task name
• add an estimate to a task
• edit estimate
• mark a task as completed

The Pomodoro Technique prescribes a longer break, typically 30 minutes after 4 completed work timers (and the breaks in between) have been completed. The application should track the number of completed timers from the start of a day and offer the user a chance to time a longer break.