-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement speed test and health check for Cap desktop app #73
Comments
/bounty $500 |
💎 $500 bounty • CapSteps to solve:
Thank you for contributing to CapSoftware/Cap! Add a bounty • Share on socials
|
/attempt #73
|
@richiemcilroy Could I get this assigned? I would like to work on this and complete this ASAP |
/attempt #73
|
/attempt #73 Options |
💡 @neo773 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
💡 @webbdays submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
Sorry for the slow progress here. Over the last couple of months we have completely redeveloped the app from the ground up, leading to the launch of Cap v0.3.0. It's a different architecture (Tauri v2 + SolidJS). |
Need to implement the following functionality into Cap:
Speed test: A small indicator in the bottom left or right of the Cap desktop app which shows an indication of the current upload speed. Depending on the upload speed, we should be using different quality types in the recording process. Right now we are using
Resolution::Captured
, but we should be using a smaller size depending on the current upload speed. Also, we need to not perform speed checks once a recording has already started.Health check: A function which runs on startup to test whether or not uploading is possible. It will attempt to upload a screen recording test to an endpoint created via the Web App (API route). Depending on the outcome, show an indicator in the Cap Desktop app to let the user know that something went wrong and to contact support. This might need to be a little bit more defined but we can discuss this.
This will allow us to be able to control the quality of the outcome of Cap's currently being recorded, and have less frustration when a user tries to record a Cap and it ultimately failed because of upload speed, or a recording issue.
Would love to work closely with whoever takes on this task - looking to get it implemented ASAP!
The text was updated successfully, but these errors were encountered: