code4romania / code4romania/teacher-workout-ios

Implement finished lessons list

Open
#11 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Swift
Stars
2
Forks
11
PR merge metrics
No merged PRs in 30d

Description

[The Figma document](https://www.figma.com/file/uLiqrlxmOB5xCppIzmiUXV/Teacher-Workout?node-id=0%3A1) contains the entire UI of the project.

You can export any image (asset) directly from Figma. [Here's how](https://drive.google.com/file/d/1KJncuAGFvKEo6zrjC9H3O59auITE0q2h/view).

**Please do not try to recreate the UI design exactly.** Prioritize using de default UI mobile components and following the [Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines/ios). The UI objects should be positioned roughly the same as in the Figma screens.

[The mobile flow can be found in the project Wiki](https://github.com/code4romania/teacher-workout-backend/wiki/Teacher-Workout-Mobile-flow).

_Please define related colors and text & button styles in the corresponding values files. Please extract all text values in the corresponding Localizable files so we can easily adjust them. <3_

---

When a user clicks on any of the lesson theme names, or the **Lecții parcurse** button in their profile page, under **Rezultate**, they should be taken to a list that contains all the lessons they have finished (filtered by theme, if the user clicked a theme name). These lessons will be pulled from the appropriate backend endpoint.

This list should be similar to the default lessons list.

![image](https://user-images.githubusercontent.com/14028425/123418291-8d3e3200-d5c1-11eb-8488-4231a89956d5.png)

Contributor guide

Open the contributing guide

Research direction

Start with the default lessons list and the profile page's Results section, then review the linked Figma document and mobile-flow wiki page for the intended screens. Identify the appropriate backend endpoint and existing navigation pattern. Done means users can open finished lessons from a theme name or “Lecții parcurse,” optionally filter by theme, and see the results in a similar list with localized text and shared styles.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.