Skip to content

qqqllppp/livethree-closed-beta

BranchesTags

Repository files navigation

WARNING: rmb to change firebase & web3auth to moonlight when testing for dev

testsetest ui

Notes:

=> firebase preview deploy: firebase hosting:channel:deploy <preview_name> --expires 1d

=> firebase offical deploy option 1 (from preview - clone): firebase hosting:clone SOURCE_SITE_ID:SOURCE_CHANNEL_ID TARGET_SITE_ID:live

  • SOURCE_SITE_ID and TARGET_SITE_ID: These are the IDs of the Hosting sites that contain the channels. -- For your default Hosting site, use your Firebase project ID. -- You can specify sites that are in the same Firebase project or even in different Firebase projects.

  • SOURCE_CHANNEL_ID: This is the identifer for the channel that is currently serving the version you want to deploy to your live channel. -- For a live channel, use live as the channel ID.

EXAMPLE: firebase hosting:clone livethree-d1d85:SOURCE_CHANNEL_ID livethree-d1d85:live

=> firebase offical deploy option 2 (from local): firebase deploy --only hosting

ref: https://firebase.google.com/docs/hosting/multisites?authuser=0&hl=en#set_up_deploy_targets

=== livethree-d1d85 || livethree-landing-page

preview template: firebase hosting:channel:deploy --only --expires 1d preview example : firebase hosting:channel:deploy test1 --only livethree-landing-page --expires 1d

deploy template: firebase deploy --only hosting: deploy example: firebase deploy --only hosting:livethree-landing-page

clone = deploy preview to live clone template: firebase hosting:clone <SOURCE_SITE_ID>:<SOURCE_CHANNEL_ID> <TARGET_SITE_ID>:live clone example: firebase hosting:clone livethree-landing-page:test1 livethree-landing-page:live

firebase hosting:channel:deploy upgrade6 --only livethree-d1d85 --expires 1d

firebase hosting:clone livethree-d1d85:upgrade5 livethree-d1d85:live

localhost will run .env.development secrets [yarn start] production will run .env.production secrets [yarn run build] ref: https://stackoverflow.com/questions/42458434/how-to-set-build-env-variables-when-running-create-react-app-build-script#:~:text=npm%20start%20will%20set%20REACT_APP_NODE_ENV,env.

Before close beta

  • connect wallet

test

during closed beta

  • upgrade Alchemy so dont hit limit (have buffer - check daily!!)

  • upgrade 100ms so dont hit limit (wait meeting tonight)

  • upgrade Web3Auth so dont hit limit (pay by invoice)

  • apply SF grant (in progress Reactor or WavePool)

  • apply polygon grant (meh, need 500 twitter follower)

  • apply 100ms grant? (startup got special starting rates)

Enhancements - must haves

  • do testing driven development when rework the livethree app | https://www.youtube.com/watch?v=04BBgg8zgWo&ab_channel=LaithAcademy | https://www.youtube.com/results?search_query=react+testing

  • make if suddenly network(chain) for some reason, pending call or active call is cleared properly

  • FORGOT PASSWORD at sign in page

  • CallsPage.tsx history uses OLD data, how to sync in map?

  • do a "in the works"/"coming soon" features such as screen share / live streaming

  • proper receipt (how much spent) in historic calls

  • todo reduce cost, can we get useDocument data from useCollection? (Call.tsx using both, manybe can only use one)

  • FIRESTORE RULES - history - see TODO in Could Firestore Tab's Rules Tab

  • prettify auth verification & password reset WEBSITE

  • handle blocked popup (if got any case)

  • enforce app check for firestore, storage, cloud function | https://www.youtube.com/watch?v=DEV372Kof0g

  • screen share

  • interactive live streaming

  • proper typescript

  • vite (instead of CRA - create-react-app): https://vitejs.dev/ (vs Next.js?)

  • best practices for firebase Auth & Firestore (ignore the class instead of hooks): https://www.youtube.com/watch?v=knk5Fjrpde0&ab_channel=Firebase

  • use-react-forms + mui: https://react-hook-form.com/ || https://github.com/dohomi/react-hook-form-mui

  • use react-query for firebase stuff and others, one down side of the current react-firebase-hooks is that cannot control the state of error and cost

  • make can delete active stream as recipient as well (not only sender - current)

  • handle cookies, apparently LiveThree uses cookies unknowingly (more than just from web3auth)

  • use server-side listener to listen when peer exit room, then trigger end [CFA money stream, delete firebase firestore & delete 100ms room (if need)] (listen to what to initate end trigger?: 100ms's webhook? how to implement this?) ref: https://www.100ms.live/docs/server-side/v2/foundation/webhook ref: we don't have any short term plans for this(and it's quite difficult to do it in generic way, there are a lot of web server frameworks), but I can defintiely point you in the right direction. Webhooks are only about setting up an api server, if you want to go with Python the easiest way to do this is using Flask. Here is a simple blog demonstrating this - https://www.realpythonproject.com/intro-to-webhooks-with-and-how-to-receive-them-with-python/ For just seeing how the webhooks responses will look like you can use this site - https://webhook.site/ to get a webhook url and put in dashboard's developer section, the UI will then show all the incoming webhooks. Possible to webhooks for SPAs? to consider revamp version of app.livethree.xyz | OR | if say use Next.js part server style and deploy to hosting, auto have a server to "listen"?

resources for webhook to close money stream:

  1. webhooks 101: https://www.youtube.com/watch?v=41NOoEz3Tzc&ab_channel=freeCodeCamp.org | https://github.com/TwilioDevEd/webhooks-course/blob/main/code/express-discorder/server.js
  2. webhooks in firebase cloud fn: https://firebase.google.com/docs/functions
  3. use reason: https://www.100ms.live/docs/server-side/v2/foundation/webhook#peer-leave-success (for 3.) how to distinguish between normal "end call" vs "non-explicit end call" such as window closed / pc shutdown, also, prevent double deleteFlow fn call. - ANS: use peer.leave.success unexpected reason (must test): https://www.100ms.live/docs/server-side/v2/foundation/webhook#peer-leave-success

Enhancements - good to consider

require register https://www.google.com/recaptcha/admin/create

all test cases for video call

Pre-call

  • change tabs and press chrome's back button
  • refresh/exit from caller side
  • pending call - end from caller side
  • pending call - end from callee side
  • wait expire pending

Normal-call-end (active call end using end icon)

  • caller side
  • callee side
  • wait expire active **

Unexpected-end --- active call, from callee side ---

  • close tab
  • close window
  • refresh
  • press back --- active call, from caller side ---
  • close tab
  • close window
  • refresh
  • press back

------ cannot reliably delete flow for cases below, make a "do not leave this page" warning ------

--- after accept call, before video load, after tx send, from callee side --- ***

  • close tab
  • close window
  • refresh
  • press back --- after accept call, before video load, after tx send, from caller side --- ***
  • close tab
  • close window
  • refresh
  • press back --- after accept call, before video load, b4 tx send, from callee side --- ***
  • close tab
  • close window
  • refresh
  • press back --- after accept call, before video load, b4 tx send, from caller side --- ***
  • close tab
  • close window
  • refresh
  • press back

About

No description, website, or topics provided.

Resources

Readme
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

No packages published

Languages