javier
e6e9afe7fa
This PR contains the work done to define the necessary setup from which the app will be built upon. To provide further details on what has been done: * created the app, the unit tests and the UI tests targets in the Xcode project; * updated the bundle identifiers and OS deployment targets of all targets; * added a `.gitignore` file tailored specifically for the project; * added a `README` file that defines in details the goal of the project; * added the [Swift Format](https://github.com/swiftlang/swift-format) rules that the source code should abide to; * cleaned the boilerplate source code on all targets. Reviewed-on: rock-n-code/todos-app#1 Co-authored-by: Javier Cicchelli <javier@rock-n-code.com> Co-committed-by: Javier Cicchelli <javier@rock-n-code.com>
17 lines
1.3 KiB
Markdown
17 lines
1.3 KiB
Markdown
# TODOS
|
||
|
||
A simple, small but complete todo app created for a technical interview with [Bol](https://www.bol.com), built using [SwiftUI](https://developer.apple.com/swiftui/).
|
||
|
||
In a nutshell, this basic app should allow a user to either create, update, and/or delete tasks; as well as being able to mark tasks as completed.
|
||
|
||
Given the requirements, the app should comply to the following criteria:
|
||
|
||
* each task should have a title, optional description, due date, and a flag indicating if it’s completed.
|
||
* tasks should be grouped visually by their due date, such as Today, Upcoming, or Past.
|
||
* users should also be able to reorder tasks within a group using drag and drop functionality.
|
||
* data should be saved and loaded asynchronously, and the UI should remain responsive while these operations take place.
|
||
* should be possible to simulate delays with built-in tools if needed.
|
||
|
||
Furthermore, the app is required to be built using SwiftUI with a clear structure that separates concerns. Any architectural style can be used, but the reasoning should be visible in how the code is organized.
|
||
It is expected that the app is modular and maintainable, so the source code must reflects this requirement. It is optional to include testable parts and anything extra that might improve the app.
|