Skip to content

Application Flow and Architecture

Lidor Eliyahu Shelef edited this page Apr 16, 2021 · 4 revisions

Application Flow & Architecture

Flow:

User Registration

  • User open the application
  • User authenticate with Facebook
  • User unique ID is returned to the app
  • User registered in our database ( the user is prompted to fill out a registration form inside the application )
  • User is registered!

User Login

  • User open the application
  • If the user is not a first time user
    • automatically logged in the app using local database
  • IF the user is a first time user
    • authenticate with Facebook
    • User unique ID is returned
    • check if the user exists in our database
    • if yes log in if not go to User Registration
  • User is logged in!

Create Event

  • User click the plus sign
  • User fill event form specifications
  • New event created!

Join Event

  • User click on event ( in map or in list of events )
  • Event dialog is opened and user see the event details
  • User asks to join this event ( join button click )
  • Event creator approve / not approve the join request
    • approved
      • the two users can chat until the meetup
    • not approved
      • join request is canceled

User delete event ( Only if the user is the event creator )

  • User go to his events list
  • User click on the delete button
  • Notification is being sent to all the attendant users
  • Event is deleted!

Create new post in bulletin board ( Only Admins )

  • Admin create a post via Firebase console
  • Notification is sent to all users that didn't turned this option off ( Not a must - check for this step in the future )
  • Posts list is refreshed to all users
  • Post is created!

Architecture: