Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mobile - Milestone 1 Review #389

Closed
rburaksaritas opened this issue Oct 24, 2023 · 1 comment
Closed

Mobile - Milestone 1 Review #389

rburaksaritas opened this issue Oct 24, 2023 · 1 comment
Assignees

Comments

@rburaksaritas
Copy link
Contributor

rburaksaritas commented Oct 24, 2023

Description

A review of Milestone 1 for the Mobil team will be conducted, ensuring that all objectives and deliverables outlined in the project plan so far have been met and are functioning as expected.

Date

29.10.2023

@egecans
Copy link
Contributor

egecans commented Nov 3, 2023

It's ok for mobile as far as I see.

I added this for deliverables, but I think that's not the purpose. Anyway, the summary of what we did is here.
Mobile

  • Added a simple homepage, toggle bar, navbar to navigate to other pages.
  • The UI part of the profile section was implemented with dummy information.
  • Network manager was created for backend connection. In this way; authentication, and resource need connection was provided easily.
  • Page layouts are created. Decided where to go from which page and showed with simple pages.
  • Login and registration for authentication were completed by connecting to the back-end. The UIs of forgot password, change password sections are ready, waiting for back-end to make end-points.
  • A simple maps page was created for the customer to visualize.
  • Need, Resource, Action, Event, Emergency and Profile tables were created for the local database in accordance with MVVM. Connection with UI is provided through ViewModels. These objects are defined and called in a single place with Dependency Injection.
  • Creation forms were prepared for Need and Resource.
  • Resource Entities created in the form of adding Resource were stored in the database in the back-end and all stored resource objects were shown on the Resource page with recycler-view.
  • Need Entities created in the Need addition form were stored in the local database and shown with recycler-view on the Need page.

@egecans egecans closed this as completed Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants