Complete add group implementation. The UI is implemented, but the API is not linked.

Please check swagger https://api.deurgenta.hostmysite.ro/swagger/index.html and complete functionality for:

• add new group
• • after the success response is received from the API, the group related info should also be stored locally in the db

Design main backpack fragments.

Please define related colors and text & button styles in the corresponding values files.

Clicking on the rucsacul meu option, should take the user to the next fragment. Clicking on aminteste-mi ...should take the user back to the home screen.

Add an enum for the backpack categories, as the category id should be sent to the backend when saving a new backpack item. These are:

1 - apă și alimente
2 - articole de igienă
3 - trusă de prim ajutor
4 - documente
5 - articole de supraviețuire
6 - diverse

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Design course type picker fragment.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Design main courses details fragment.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Implement the forgot password related screens.

Please define related colors and text & button styles in the corresponding values files.

to be added: reset password endpoint

After reseting the password, the user should be redirected to the login screen.

Link to design in Figma

Design about app fragment.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to design in Figma

Complete backpack implementation. The UI is implemented, but the API is not linked.

Please check swagger https://api.deurgenta.hostmysite.ro/swagger/index.html and complete functionality for:

• list items from a backpack
• add / edit / delete backpack items
• after the success response is received from the API, the backpack items related info should also be stored locally in the db

Design add backpack item fragment.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Implement the create account form screen as a fragment in the Login Activity.

Please define related colors and text & button styles in the corresponding values files.

to be added: create account endpoint

Link to design in Figma

Implement the login form screen as a fragment in the Login Activity.

Please define related colors and text & button styles in the corresponding values files.

to be added: login endpoint

After a successful login, the user should be redirected to the onboarding activity if onboarding was not completed and to the main activity otherwise.

User data (name, access token) should be saved in shared preferences.

Link to design in Figma

Building the project in Android Studio produces warnings such as:

The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.

According to this Android Developers Blog post, the old kotlin-android-extensions will be removed in a Kotlin release during or after September 2021, so we should update our dependencies before then.

Design backpack items list fragment.

Please define related colors and text & button styles in the corresponding values files.

If the items list is empty, show an empty state message.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Implement the login landing page as a fragment in the Login Activity.

Please define related colors and text & button styles in the corresponding values files.

Link to design in Figma

@aniri Is the backend completely implemented for resetting the password?

I see the endpoint /auth/request-reset-password which has a correspondence to a screen in the application (02.2) , but this endpoint seem to just send a reset email.

For screen 02.3 I'm assuming that we should hit endpoint /auth/reset-password, but what should we use for userId and resetToken if the previous endpoint doesn't return anything?

Any thoughts on this?

Design home screen for main activity.

Please define related colors and text & button styles in the corresponding values files.

Please use navigation drawer and material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :)

Link to design in Figma

Steps to reproduce:

• go to configure addresses
• the map will center on your current location
• search for an address -> the map moves to the new address
• wait a few seconds
• the map jumps back to the users current location

Expected behaviour:

• the map should not jump back to the current user location

On small screens, not all menu items are available while scrolling.

Implement an easy to use error handling mechanism.

Should support displaying snackbars and dialogs. Check the design in Figma for hints on how to design them, but follow the android material design guidelines for them.

These should be displayed easily in case of validation or api errors.

Redirect to login in case auth errors are received from the api. The rest of the api errors should be displayed in a dialog. TBD: api error format

Also, for certain requests, a snackbar error should be shown in case the user attempts to make the api call but is not connected to the internet.

Design course details fragment. All the info to be displayed with be returned by the api.

The inscrie-te button will open the browser to a certain url from the course properties.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Navigation should work from onboading screen, main screen and menu.

Currently not all screens are reachable from all of the above options.

To be fixed in this issue -> navigation from side menu and home screen:

Onboarding screen:

Side menu:

items to be fixed:

• emergency backpacks - should navigate to the same screen backpacks screen that is currently available only from onboarding

Home screen:

items to be fixed:

• grupul de urgenta - should navigate to the same screen as from the emergency groups menu item
• rucsacul de urgenta - should navigate to the same screen backpacks screen that is currently available only from onboarding

Depends on #58 and #60

Adding a new member should only be allowed from the edit group screen:

Please add proper permission handling for requesting access to contacts.

After clicking the add new member option and allowing access to contacts, the list of contacts should be displayed, similar to:

The button at the bottom of the screen is not needed, only the buttons next to each contact should be added. Pressing the button should open the send sms app with a custom text pre-filled (the text should be extracted in the strings file).

To be implemented in the future, after backend is ready: the link to be added in the sms should be retrieved form the backend.

Implement add new group member functionality. Link to API in swagger

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Depends on #58

Design edit group fragment.

Please ignore the "Invitație trimisă" link for now.

The API calls for editing a group are implemented. Link to API in swagger

Please complete ui navigation between fragments.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Implement the address type picker fragment in the Onboarding Activity.

Please define related colors and text & button styles in the corresponding values files.

Some basic scaffolding was added, but it needs to be cleaned up.

the types should be retrieved from the backend. endpoint to be decided. code4romania/de-urgenta-backend#51

Link to design in Figma

Implement the add address flow as reusable fragments.

Use them in the Onboarding Activity:

• the first time the user selects the option to add a new address, the flow should start with the address type set to home
• after adding the new address, the screen with the list of added addresses should be displayed with the option to add another address
• the following time the user chooses to add a new address, the address type picker should be displayed first ( depends on #12 )

The addresses should also be stored locally after the success response from the backend.

In case there is no internet connection when the user tries to save the address, an error should be displayed ( depends on #8 )

Please define related colors and text & button styles in the corresponding values files.

Some basic scaffolding was added, but it needs to be cleaned up.

Map provider: here maps
to be added: save address endpoint

Link to design in Figma

Design main menu and setup for navigation between the main activity fragments.

Please define related colors and text & button styles in the corresponding values files.

Please use navigation drawer and material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :)

Link to design in Figma

The https://www.figma.com/file/d6n3MPVRWbL5jP2NmvW96b/De_Urgenta?node-id=1466%3A530 has some parts that need to be adjusted in order to make the app respect the android material guidelines.

We could:

• use the app bar to display all screen headers / titles
• replace the x button with a more common < in the appbar for back navigation between fragments
• replace images with proper vector icons (we should request all needed icons on slack)
• standardise colors and text sizes fixed in #85

Design add group fragment.

Prepare setup for api call and ui navigation between fragments.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

The dropdown with address types should use the values loaded from the backend:

GET ​/user​/location-types

The login endpoint was implemented in the backend https://api.deurgenta.hostmysite.ro/swagger/index.html

Please add it in the app, the layout for the login page is already implemented.

Link to design in Figma

Complete backpack implementation. The UI is implemented, but the API is not linked.

Please check swagger https://api.deurgenta.hostmysite.ro/swagger/index.html and complete functionality for:

• listing user backpacks
• adding new backpacks
• after the success response is received from the API, the backpack related info should also be stored locally in the db

The register endpoint was implemented in the backend https://api.deurgenta.hostmysite.ro/swagger/index.html

Please add it in the app, the layout for the register page is already implemented.

Link to design in Figma

Implement the courses search results fragment.

This screen will show up after the user selects a course city and type and presses the view course button (#32).

This screen should only show the search results, please ignore the dropdowns from the figma design.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Complete add address implementation (feature accessible from the onboarding screen). The UI is implemented, but the API is not linked.

Please check swagger https://api.deurgenta.hostmysite.ro/swagger/index.html and complete functionality for:

• saving a user address POST ​/user​/location

Implement loading fragment.

Link to design in Figma

TBD

Check swagger https://api.deurgenta.hostmysite.ro/swagger/index.html for data model :)

Backpack item categories should be stored in an enum, as mentioned in #24

Design first add group fragment.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to API in swagger

Link to design in Figma

Design group list fragment.

When opening the screen, all groups will be stacked. When clicking on a group name, the group members list should be retrieved from the api and expanded.

The numbers in parentheses after the group name are: the number of group members / maximum group members allowed (depends on code4romania/de-urgenta-backend#68)

GET /groups/my

GET /group/{groupId}/members

An "add new group" button / link is missing from the UI. Please add one :)

The API calls for getting the group list and group members list are implemented. Link to API in swagger

Please complete ui navigation between fragments. The groups list should open from the main menu & home screen.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Design settings fragment.

Selecting the Raporteaza o problema option should open the email app to compose a new email. The to address should be pre-filled with a value stored in the properties files.

Please define related colors and text & button styles in the corresponding values files.

Please use material design guidelines for android. The figma design is a bit ios oriented, it needs a bit of adapting for android :) For example, the title should be placed in the action bar with a back button instead of the X.

Link to design in Figma

Implement the add meeting point flow in onboarding.

This flow is very similar to the one for addresses. Please reuse as much as possible from #13

The addresses should also be stored locally after the success response from the backend.

In case there is no internet connection when the user tries to save the address, an error should be displayed ( depends on #8 )

Please define related colors and text & button styles in the corresponding values files.

Some basic scaffolding was added, but it needs to be cleaned up.

Map provider: here maps
to be added: save meeting point endpoint

Link to design in Figma

The location permissions should be required when loading and using the map (add addresses feature).

Sometimes the go to settings dialog seems to show up twice even if I click ok.

After I refused the locations permission, nothing happens when I try to navigate to configure addresses. The permission should be requested again and the user should be informed that the permission is mandatory for configuring addresses.

Pull request #69 will remove the copy of the IBM Plex Sans font bundled with the app and the unmaintained FontReplacer package. We will have to switch to the official Android Downloadable Fonts API if we want to keep having a custom look and feel for our app.

Some items in the backpacks have expiration dates set for them. We need a service that will check daily if any of the items has expired. In case one of the items has expired, a dialog should be shown to inform the user.

To be decided: how often should we send reminders? What text should be displayed in the reminders?

Implement the onboarding landing page as a fragment in the Onboarding Activity.

Please define related colors and text & button styles in the corresponding values files.

Some basic scaffolding was added, but it needs to be cleaned up.

Link to design in Figma