gdgkolachi / community_app Goto Github PK

The event organizer can also at this stage only see the list of check points configured in the event data model. To add checkpoints update the data model. Checkpoints are now covered in #7

The event organizer can see the list of participants with status as REGISTERED, so they can shortlist them. As they shortlist someone, a notification/email is sent to the person. Notification is covered in #21.

The event organizer can see also post content to the message board. They should post content in markdown so the message board can support rich text. Message posting is covered in #14.

As the organizer shortlist someone, a notification/email should be sent to the person.

Remove QR code from the account screen

Allow user to update name, university/organization, designation, professional/student

After logging in using Google account, if a user profile is not found in our system, a screen should be shown to the user having following fields:

Name(required)
Phone Number(required)
Student/Professional(required)
Designation(skippable)
Organization(skippable)

The side nav should have the following items:

• Home
• Events
• About [Community]
• Notifications
• My Profile
• Log out

Organizers can post simple text messages (up to 255 characters) which will be shown in the message board.

• Loader needs to be updated as well
• Update app name to GDG Kolachi
• App icon need to be updated

Add support in event data model to mark a user as a volunteer or organizer. These users will see a MANAGE button on that event's detail page.

Show feedback messages on following screens:

1. Event listing
2. Incoming registrations

User should be redirected to the about screen, where we have a text description and social channels listed as:

Facebook - https://www.facebook.com/GDGKolachi
Twitter - https://www.twitter.com/GDGKolachi
Instagram - https://www.instagram.com/GDGKolachi

The fields of the registration form should be fetched from the database and the form should be generated dynamically.

The schedule tab should be dynamic in handling a multi date schedule. This means that the schedule will have filter for date.

The third tab of event detail (#5) should be a message board from the organizers where they can post different messages and links etc.

Message posting is tracked in #14.

The event volunteer can only see the list of check points configured in the event data model. The common check points could be: ATTENDANCE, LUNCH, GOODIE BAG

The volunteer can tap on any one of these, and it will open up a QR code scanner which will enable them to scan confirmed participants QR code, on successful scan, user status for the check point will be updated.

Organizer can also perform these operations.

Checkpoints to be added directly in FireStore.

The QR code on the user profile page will be used by the volunteers to scan it at various checkpoints (see #7).

GET STARTED Action fails if user profile has no occupation

The home screen should show a list of upcoming events only. Each list item should show the following data points:

• Event Name
• Event Date
• Event Location
• Event Feature Graphic
• User Status for the event [UNDEFINED(Register),REGISTERED(Shortlisting Pending),SHORTLISTED(Confirm Registration),CANCELLED(Re-apply), CONFIRMED]

If the user status is UNDEFINED, the CTA text should be "Register", on tapping it the user should be redirected to the event registration form. The fields of the registration form should be fetched from the database and the form should be generated dynamically. Dynamic registration form is tracked in #12.

If the user status is REGISTERED, the CTA text should be "Shortlisting Pending", on tapping it the user should be shown a popup that their registration is pending and they will be notified when they are shortlisted.

If the user status is SHORTLISTED, the CTA text should be "Confirm Registration", on tapping it the user should be shown a popup that they have been shortlisted, and they can confirm themselves or cancel their registration. Based on the button pressed user status is updated. If a user presses confirm after 24 hours(this variable is to be configurable on per event basis), the user will be notified that their registration was cancelled

If the user status is CANCELLED, the CTA text should be "Re-apply", on tapping it their status is updated to REGISTERED.

If the user status is CONFIRMED, the CTA text should be "View Event", and it takes the user to the event details screen.

In general, when the user taps the list item the user is taken to the event details screen.

We should be able to enable and disable a version of the app remotely so we can force our users to update the app

We can use Firebase Remote Config for this: https://pub.dev/packages/firebase_remote_config

This will feature an image and a background solid colour, which should be configurable from a properties file when building the project.

The event details screen should have 3 tabs, first tab should be the summary, which should have the event name, date, location, feature graphic, description about the event. The second tab should be the schedule, the schedule tab should be dynamic in handling a multi day (tracked in #11) and multi track (tracked in #10) schedule. This means that the schedule will have 2 filters, for date and track. The third tab should be a message board from the organizers where they can post different messages and links etc. Message board is tracked in #13.

Admins(or at this point even from the backend using some script) we should be able to add a message for all users, and then send a push notification about it.

• Show message on message board
• Acquire Apple and Google developer license
• Configure app for push notifications on Firebase
• Add push notification handlers

The schedule tab should be dynamic in handling a multi track schedule. This means that the schedule will have filter for track.

When you approve a registration, it's removed from the list as expected. If you go back to the previous page and return back to registration list, the approved entry is shown again.

This is happening because the event object itself is not refreshed and the instance is passed from the listing page -> event detail page -> registration page.

Dev apps should have a suffix .app in the end so that they don't collide with prod apps. We should also allow check in the dev config files.

Event organizers will be able to see the list of registered user with an action against each registered user to accept or reject their registration request. On accepting the request, the user will be marked as shortlisted.

For an Organizer or Volunteer the event detail tab will show a manage event button. Tapping on this button will take them to the event management screen. This means that the event data model will have the ability to mark a user as a Volunteer or Organizer.

The event detail page should show an action similar to the event listing page to let the user register/confirm etc from within the event detail page too.

Widget will show empty message or content based on the content length