Questions 12/27 Tue:
We are splitting the project into individual parts and then we will integrate them together.
Every part of the task will have its own github repository.
Every part of the task will need to be deployed on its own vanity url (such as dev1.1.country or dev33.1.country, ect.)
Big overview: videos will have payment(though stripe), gated access(per video/per page), one click mute, swipe gestures, full screen(rotatable), auto generated transcripts/captions (mux)
Jan 10, 2023
First, user navigates to video.demos.country - the first video will be playing (url: video.demos.country/1)
- User can swipe right next video
- User can swipe left for previous video
- User can swipe up to upload a video
- When there is a video uploaded a new vanity link will be created such as if there are already 4 videos the next video uploaded will be /5
- User can swipe down to view the video gallery
- Scaleable image for mobile and web based on screen size
Every thing is Mobile Optimized
Name | Person | Priority | Effort | Deadline | Parent item | Sub-item |
---|---|---|---|---|---|---|
Frank Egloff | Now | December 29, 2022 | ||||
Now | December 29, 2022 | |||||
Artem Kolodko | Now | 6 hours | January 5, 2023 | |||
Frank Egloff | Now | |||||
T Tejassvi Kaushal | Now | January 13, 2023 | Vanity URL access control for web3 integrationdata structure design compatible with current VanityURL contractStore the Vanity URLs each user has the right to accesscheck if the user have the right to access to the specific Vanity URLreset all the information if .1.country NFT is transferred from the creator to another addresswrite the test scriptsdeploy the contracts on mainnet shard0support the smart contract integrationOne touch pause/playfunctioning button | |||
Artem Kolodko | Now | January 4, 2023 | ||||
Frank EgloffSergey Karasev | Now | January 3, 2023 | ||||
Frank EgloffArtem Kolodko | Now | 3 hours | ||||
Soon | ||||||
Soon | ||||||
T Tejassvi Kaushal | Soon | |||||
Anytime | ||||||
Anytime | ||||||
Anytime | ||||||
Anytime | ||||||
Anytime | ||||||
Anytime | ||||||
Frank Egloff | Done | December 29, 2022 | ||||
Frank Egloff | Done | 3 hours | January 5, 2023 | |||
Frank Egloff | Done | |||||
T Tejassvi Kaushal | Done | January 13, 2023 | ||||
T Tejassvi Kaushal | Done | January 13, 2023 | ||||
T Tejassvi Kaushal | Done | January 11, 2023 | ||||
Sergey Karasev | Done | 6 hours | January 3, 2023 | |||
Sergey Karasev | Done | |||||
Sergey Karasev | Done | 1 hour | ||||
Sergey Karasev | Done | 1 hour | ||||
T Tejassvi Kaushal | Done | January 9, 2023 | ||||
Frank Egloff | Done | December 29, 2022 | ||||
Frank Egloff | Done | December 29, 2022 | ||||
T Tejassvi Kaushal | Done | January 6, 2023 | ||||
T Tejassvi Kaushal | Done | January 5, 2023 | ||||
January 4, 2023 | ||||||
December 30, 2022 | ||||||
January 5, 2023 | ||||||
Current version
Hey guys, after yesterday’s meetings with Abhinav, Li and Tej, and today’s meeting with Artem, it will be better to work on 1.country repo because this project is a new feature of the user domain page. We need to add the following items:
- Creators can upload a video to their domain page
- Upload video form (@Frank Egloff)
- For this, we need video transcoding (services like coconut/mux) (@Sergey Karasev)
- Require Amazon S3 bucket for raw video
- Users can subscribe to see the creator’s videos. Subscribing requires payment from the user.
- First version Fiat payment through stripe integration (@artem Kolodko)
- Later version could include SMS wallet.
- Users can pay-per-view one video.
- First version Fiat payment through stripe integration (@artem Kolodko)
- Later version could include SMS wallet.
- Users watching a video can press the payment button to purchase merchandise linked to the video.
- Task: Discussion with Abhinav/Li to find out the input fields of the upload video form because the pay button should be enabled only for videos with merchandise linked.
- Web3 integration (@tejassvi Kaushal)
- There are 3 payment steps in total.
- Pay to access the creator’s video list (store on chain)
- Pay to watch the specific video (pay-per-view) on the creator’s vanity url (store on chain)
- Pay to purchase merchandise linked to the video (don’t store on chain)
- The information for the 1st and 2nd steps will be stored on chain
- Information to store on chain
- user wallet address
- user wallet address → vanity URL to access the creator’s video list (1st step)
- user wallet address → vanity URL list to access the creator’s pay-per-view video (one video) (2nd step)
- information to provide
- store the vanity URLs the user can access to watch the creator’s video list or pay-per-view video.
- check if the user has the right to go to the specific vanity URL to access the creator’s video list or the creator’s pay-per-vie video
- The information should be handled by our BE only.
- If the user paid to access the specific vanity url before, he/she doesn’t need to pay again to access that url.
- We’ll require the user to connect the metamask before displaying the video list or the video on the vanity URL so that we can check if the user has the right to access the specific vanity URL.
- If the .1.country NFT is transferred from the creator’s wallet address to another wallet address, all information related to that NFT will be reset(removed).
This will prevent the user who didn’t pay go to the vanity URL directly to watch the video.
Users can see videos under a certain domain, such as abhinav.1/videos
- When a user navigates to abhinav.1/videos they will see the videos that have been uploaded
- a user can click on a video and swipe to go to the next video under abhinav.1/videos/..
- video 1: abhinav.1.country/videos/watch swipe to video 2: abhinav.1/videos/music, swipe to video 3: abhinav.1/videos/coffee
- every video uploaded to abhinav.1/videos will have its own vanity URL, , such as abhinav.1.country/videos/watch, abhinav.1/videos/music, abhinav.1/videos/coffee
Video post
- Immersive like TikTok (full screen, autoplay, one-click upload), minimal like Tinder (touch pause, touch mute, swipe navigate), optimized like YouTube (multiple sizes, edge network, offline cache), actionable like Shopify (shoppable links, Apple Pay integrated, merchandise checkout)
- the user will be able to interact will all options on the video in both portrait and landscape mode (in full screen)
- Interactions:
- Apple Pay buttons for merchandise purchases
Upload page
- Compatible with mobile upload through photos and files.
Checkout Flow (Artem)
- there will be a buy button on top of the video
Video transcoding (@Sergey Karasev)
- use mux (https://www.mux.com/real-time-video)
some ideas
Previous version + questions
Video Reel
- What videos could the user see?
- Users that the user follows?
- The entire video database?
Video post
- Do we want users to interact with the video post?
- Could the user interact with the post in portrait and landscape mode?
- the user will be able to interact will all options on the video in both portrait and landscape mode (in full screen)
- What kind of interaction?
- Likes?
- Emojis?
- Comments?
- Share Button?
Portrait view
Tik Tok
- What design should we aim for? TikTok has the video as a background with interaction buttons on top of it.
- Immersive like TikTok (full screen, autoplay, one-click upload), minimal like Tinder (touch pause, touch mute, swipe navigate), optimized like YouTube (multiple sizes, edge network, offline cache), actionable like Shopify (shoppable links, Apple Pay integrated, merchandise checkout)
- What video metadata has to be shown?
- Creators ONE ENS fegloff.one/video, fegloff.one/video4
- Video description
- maybe have auto-generated comments
- Number of likes
- none, just video commerce for now
- Add a mute button to the video.
Landscape View
- Neither Instagram nor TikTok allows video rendering in landscape view.
- Will the user be able to interact with the video in landscape view?
- Add a mute button to the video.
User Profile
- What information needs to be registered by the user?
- ONE ENS (required) ⇒ fegloff.one
- Wallet address (required)
- Full name
- Phone number
- Gender
- Age
- Country
- Which user information is public to other users?
Upload page
- Compatible with mobile upload through photos and files.
- Video description or Tags.
Wallet/Web3
- Only the creator needs a wallet/domain
- The visitor/user won’t need a wallet.
- Payment will go through Apple Pay(stripe integration).
- Does the user need to have a wallet to use the app?
- Does the user need to have One ENS registration to use the app?
- Creating ONE ENS could be a requirement to use the account.
- What operations must be approved/signed by the user wallet?
- Does the user has to pay for each video post-interaction?
- Would each interaction have a different price?
- What operations will have associated costs?
- Free video upload for user's account or friends
- Pay video upload for videos that can reach all users
- Pay++ for video upload for videos that can reach a user's segment (age, gender).
NOTES: