Skip to content

Releases: softeng-feup/open-cx-mr-simba

Iteration 4- Agenda Mobile App v4.0

18 Dec 16:36
e74bf31
Compare
Choose a tag to compare

(Finished 8th December 2019)

On iteration #4, some additional but also very important features were added, like the generation of a notification roughly 10 mins before a session beggins; the ability to create custom sessions and add them to a day's schedule; a search bar for the sessions, etc. The display of information about the sessions, items and people was finalized.

Iteration 3- Agenda Mobile App v3.0

18 Dec 16:36
Compare
Choose a tag to compare

(Finished 26th November 2019)

On iteration #3, the main focus was the implementation and usage of a local SQLite database, in order to keep information about the conference and the user schedules for the different days. The bluetooth functionality was fully implemented, and some visual aspects of the app were refactored. Furthermore, some additional information about the sessions, items and people also started to be shown to the user.

Iteration 2- Agenda Mobile App v2.0

18 Dec 16:35
cc93f08
Compare
Choose a tag to compare

(Finished 5th November 2019)

In this iteration, the main focus revolved around 2 things: the start of the implementation of the bluetooth functionality, and the organization and structuring of the code, in order to follow the logical architectural patterns that were discussed in the beginning.

Iteration 1- Agenda Mobile App v1.0

18 Dec 16:34
Compare
Choose a tag to compare

(Finished 25th October 2019)

In iteration #1, we spent a considerable amount of time learning about Flutter. Despite this, in order to start seeing results and verify our bet on the technologies we chose, we quickly started implementing the basis of the app to deal with our most important user stories.

Our first real prototype of the app consists essentially of the barebone of the agenda part of the app, and it allows the user to consult conference sessions by day and save the favourites in a personalized list.

The implemented user stories were #1 and #2. These stories are closely related and were implemented by having a button in the main screen for each day of the conference, allowing the user to navigate to a screen where his favourite sessions for that given day are shown (user story #2). In this screen, by pressing the ADD button, the attendee can consult information about all of the sessions for that day (user story #1), and add the ones that interest him the most
to his personal schedule.