squanchy-dev / squanchy-flutter Goto Github PK

Display MVP data about the event:

• Title
• Speaker(s) — name(s), photo(s)
• Timestamps — start, end
• Room
• Abstract OR, if not a talk-like event, the corresponding illustration
• [if user is signed in] Favourite state

Clicking the speakers should bring up the speaker details.

Clicking the favourite button should toggle the favourite state if the user is signed in, otherwise should bring up a sign-in prompt.

🗒 Sharing an event is out of scope for this story

Please refer to @ScribblyPixels' design.

⚠️ The design for this screen is not finalised yet

Assuming tweets are retrieved by a cloud function and they're stored in Firestore, the app should fetch them.

Details TBD.

• Appbar
  • Back button
  • Text field
  • Voice input button (not functional)
• Empty state
  • Topics (tracks)
  • Speakers

🗒 The search results is implemented in another story, #12

Example (Android):

Please refer to @ScribblyPixels' designs

Data:

• Timestamp (HH:MM)
• Speaker pic(s) and name(s)
• Experience level
• Title

Example:

Please refer to @ScribblyPixels' designs.

On iOS 11+ it's possible to set up a hotspot for the user. If we have the wifi informations in the app configuration we should be able to offer users to automatically set up the WiFi for them.

🗒 UI is in the onboarding (#46) and in the settings (#49)

🗒 Error UI is handled in #47

Seems the AppBarBottomWidget class no longer exist as trying to run the app throws the following error:

class FlexibleAppBarBottomWidget extends AppBarBottomWidget```
And the [flutter docs](https://docs.flutter.io/flutter/material/AppBarBottomWidget/bottomHeight.html) show a Not found error

The app should have a pluggable framework for onboarding, including:

• Ability to show onboarding on the first startup
• Never show it again
• Adding/removing pages easily at compile time
• Skipping all onboarding pages (via a "skip" button, for example)

The reference is the Android native app's onboarding framework.

Please refer to @ScribblyPixels' designs

⚠️ There is no finalised designs for this screen yet!

In addition to what is retrieved as per #23, retrieve the following info about a session from Firestore:

• Video link
• Slides link
• Other data?

Fetch speaker details from Firestore:

• Name
• Company name
• Profile pic
• Website URL
• Twitter username

Display speaker details:

• Name
• Company name
• Profile pic
• Website URL
• Twitter username

🗒 Displaying multiple speakers' data at once is in a separate ticket, #29

Please refer to @ScribblyPixels' design

⚠️ There are no designs for this screen yet

Building upon #28, if there's more than one speaker associated with a session, the user should be able to quickly switch between the speakers. E.g., they could be in a viewpager.

Please refer to @ScribblyPixels' design

⚠️ There are no designs for this screen yet

The app should obtain the schedule data from Firestore and use it to fill in the items in the schedule UI. This depends on #5

Structure:

• Appbar with menu items
  • Settings
  • Search
• Big empty space in the middle
  Empty states will come later, together with the tabs for the schedule etc
• Bottom nav bar with three items
  • Schedule
  • Favourites
  • Venue info

Please refer to @ScribblyPixels' designs.

The user should get a notification when a session they have favourited is about to start (i.e., starts in 5 minutes).

We should display:

• Session title
• Session room
• Start time

The second onboarding page is the WiFi setup page; it should look something along these lines:

Please refer to @ScribblyPixels' designs.

The "no thanks" button brings users to the next page, "yes please" starts the automatic setup process. If setup succeeds they're immediately brought to the next onboarding page (or schedule if this is the last one), otherwise they remain on the current page and some error is displayed (out of scope, see #todo).

⚠️ The existing designs are still WIP

⚠️ Blocked by #48 (implementing the WiFi setup code)

🗒 Wi-Fi setup is only available on iOS 11+

🗒 This page can only be shown if the app has the WiFi configuration data, otherwise it must be skipped.

Fetch the following info about a session from Firestore:

• Title
• Speaker(s) — name(s), photo(s)
• Timestamps — start, end
• Room
• Abstract
• [if user is signed in] Favourite state

🗒 Additional data could be fetched but it out of scope for MVP, see #24

Up to 10 recent searches — not backed up across devices (for now?)

🗒 The search results UI is implemented in another story, #12

Example (Android):

Please refer to @ScribblyPixels' designs

Display the venue information screen:

• Venue name
• Venue address
• Venue map
• Other data TBD pending screen design

Please refer to @ScribblyPixels' design

⚠️ There is no designs yet for this story

The first onboarding page is the sign-in page; it should look something along these lines:

Please refer to @ScribblyPixels' designs.

The "no thanks" button brings users to the next page, "yes please" starts the sign-in process. If sign-in succeeds they're immediately brought to the next onboarding page, otherwise they remain on the current page and some error is displayer (design TBD).

⚠️ The design for the error state is TBD and the existing designs are still WIP

When a user taps one of the tracks in the search screen initial/empty state, all talk-like events pertaining to that track will be shown in the UI

🗒 The rest of the search functionality is implemented in other stories, this is only about track search

Example (Android):

⚠️ The above screen is just a mockup as there is no design for this story yet

Please refer to @ScribblyPixels' designs

When the user starts the app for the first time they must be assigned an anonymous Firebase Auth identity so we can enforce access rules (e.g., allow reading but not writing).

• Appbar
  • User avatar and name when signed in
  • "not signed in" when not signed in
• Settings
  • Sign in CTA when not signed in
  • User email address and sign out CTA when signed in
  • Notifications settings (MVP is master toggle)
  • About
  • Version number

Please refer to @ScribblyPixels' designs

⚠️ There is no designs for this screen yet

When a user types 2 or more characters in the search field (or inputs using voice), we perform a search across:

• Events — all meaningful fields (title, description, speaker name, track name, etc)
• Speakers — all meaningful fields (name, company, bio)

🗒 The actual search is implemented in another story, #13

We then display, in separate sections (when there are hits):

• All matching talk-like events (talks, keynotes, workshops, etc)
• All matching speakers

🗒 Tapping these items should deep-link to the details, but it's out of scope for this issue.

Example (Android):

Please refer to @ScribblyPixels' designs.

Please refer to @ScribblyPixels' designs

⚠️ There is no finalised designs for this screen yet!

🗒 The licenses listing screen is part of another story, #34

If a user is signed in we should show them some CTA to add talks to their favourites:

If they're not signed in we should show them a CTA to sign in:

[design missing]

Please refer to @ScribblyPixels' designs

⚠️ Designs for this story are still not finalised/missing

Fetch venue information from Firestore:

• Venue name
• Venue address
• Other data TBD pending screen design

Data for each event in the bundle:

• Timestamp (HH:MM)
• Speaker pic(s) and name(s)
• Experience level
• Title

Example:

Please refer to @ScribblyPixels' designs.

Allow users to share links to an event using a web URL, or Firebase dynamic links.

⚠️ There is no design for this screen yet

Implement the UI (still TBD) for when the user tries searching for something and nothing matches their query.

This also includes designing and implementing other edge cases, such as:

• The user clears out the search field: do we show the inactive state again, or do we show an alternative UI like in the native Android app (which is there to simplify the screen logic)

⚠️ There is no design for this story yet

🗒 The rest of the search functionality is implemented in other stories

The app should obtain the search data from Firestore and use it to fill in the search UI. This depends on #5

The settings screen should display a "configure conference Wi-Fi" item if the device runs iOS 11+ and the app has Wifi configuration data. If the hotspot is already configured on the device, it should be marked as "already done".

⚠️ There is still no designs for this story

⚠️ Blocked by #48 (implementing the WiFi setup code)

🗒 Wi-Fi setup is only available on iOS 11+

🗒 This setting can only be shown if the app has the WiFi configuration data, otherwise it must be hidden.

When a user is logged in, they should see talk-like events they have favourited in the schedule having a distinctive mark:

Please refer to @ScribblyPixels' designs.

This is blocked by #19

• Create the iOS App configuration on the Firebase console
• Create the Android app configuration on the Firebase console
  This shares the same configuration as the native Android app so it's already set up.
• Configure the Firestore library using FlutterFire's cloud_firestore plugin
• Confirm data can be accessed from the Flutter app (no UI needed)

Whenever there is data in the schedule (i.e., not in the empty state) we need to display each day in its own tab:

Please refer to @ScribblyPixels' design

When a user types 2 or more characters in the search field (or inputs using voice), we perform a search across:

• Events — all meaningful fields (title, description, speaker name, track name, etc)
• Speakers — all meaningful fields (name, company, bio)

The results will be presented in separate groups in the UI.

🗒 The UI is implemented in another story: #12

We should display the tweets that we retrieve as part of #39. UI TBD.

⚠️ There is no designs for this story yet

When a user is signed in we should show them their favourites, organised by day (TO BE CONFIRMED). Tapping the events brings users to the details for the event.

⚠️ There is no design for this screen yet

When there's nothing in the schedule (not loaded yet? Error fetching?) then we should show an empty state. For example:

Please refer to @ScribblyPixels' design

In addition to the Google Sign in we should provide auth using other auth providers supported by Firebase Auth:

• GitHub
• Facebook
• Twitter

There will be the need for sign in UI designs once we support more of these providers.

Hello,

I tried to run current app, but it crashes on Android Emulator (Android 8.0, x64)

Im pasting output log:
output.txt

And my flutter doctor results:
doctor.txt

Lets ignore InteliJ Idea info, Im using Android Studio
Let me know if I can help with debugging

Obtain the list of favourites from Firestore for a signed in user.

🗒 The UI is done in another story

The app should be able to receive data-only push notifications via FCM so that it knows to, for example, refresh the DB data, or the remote config (if used).

Data:

• Timestamp (HH:MM)
• Image (depending on the type)
• Title

Example:

Please refer to @ScribblyPixels' designs.

The app should be able to display push notifications received via FCM.

For example in Android:

⚠️ This story has no designs yet

Allow the user to be signed in with Google, to unlock features that require a non-anonymous user, such as favourites.

⚠️ There are no designs for this flow yet

If in the WiFi setup things don't work we should show some error UI:

Please refer to @ScribblyPixels' designs.

The "no thanks" button dismisses the page, "open settings" opens the settings screen where users can manually add the network. The Copy button will copy the password to the clipboard.

⚠️ The existing designs are still WIP

⚠️ Blocked by #48 (implementing the WiFi setup code)