Tier-gated, asynchronous batch ingestion of YouTube links for Recall can eliminate user frustration, protect backend stability through quotas, and maximise monetisation by aligning high-cost AI processing with elite, corporate, and academic users.
s
software3jianfa8tsai
Problem: After pressing on the YouTube (YT) iPadOS app, share button to share the YT link to Recall knowledge management app, the Recall app opens and there is a 15 to 20 seconds+ of loading, processing or waiting time.
This creates annoyance and frustration for a few user demographics (e.g. time poor professionals or researchers).
Proposed solution:
Why not max profits by providing a feature (communicate via YouTube, website tutorials, word of mouth and advertising), where users can copy the YouTube links into their Notes iPadOS app, and export the note as as txt, md, PDF files or CMD+A to copy the list of links into the Recall app, import text box (similar to files upload function), where Recall app can run the processing in the background even after the users have immediately quit the app or power down their device after pasting the body of links or uploading their files?
To prevent abuse of the feature that cause backend issues, simply introduce a gateway where the feature is for elite tier paying customers, or just for corporate or academic customers. Communicate and restrict daily number of links that can be processed daily per account.
Log In
t
twan
I had another proposal solution to this problem where some kind of background que stores all requests to recall. It only logs the URL shared and the settings used, then the upload time is nearly zero because of low info intake. Then the que starts working on whatever is logged first without the user having to wait for recall to do its thing.
This way faster UX on the frontend and the backend can work at whatever speed it can. Having a backend sorting system you could acces (like a YT playlist) you could order the incomming logs to whatever your prefer to be done first.
I made this suggestion because of the problem with bulk importing bookmarks or playlists (not yet available). When doing this Recall does not make a summary or connections due to the high cost of importing hundreds of files at once. Which is a viable problem.
However every user has a set limit to upload per month and when reached you have to wait untill the next month. With this que they could effectively just let it run until you run out of credits and resume when the next batch arrives. This is also a perfect way to insert an upsell proposition where you can buy more credits or take a higher tier acount to get more credits for researchers ea.
I mailed this proposal straight to Recall last week, but thought I'd mention it on this platform as well :)