-
Notifications
You must be signed in to change notification settings - Fork 474
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
Reminders integration #224
Comments
I am looking into this. Which platforms do we want to support? Some that come to mind
The assistant is incentivized to create action points from the conversation. I don't think every single action point should be a reminder it would get too cluttered and no one would use the feature. So what constitutes a reminder and what doesn't? The other approach is that the assistant identifies reminders, which is potentially a subset of action points, and asks the user for confirmation to write to whichever reminders app has been selected as default. |
Hi, I would like to work on this. Can you please assign this to me? |
Assigning to @diegoasua for the next 2 days |
#307 WIP |
@josancamon19, I would like to take on this task and give it a try if it's still available. |
Hi @josancamon19, have worked on a similar task before. Can I take this? |
Assigning to @antonio-pedro99 please create a Draft PR when you get started. |
I will be there |
Hi @antonio-pedro99 if you could create a Draft PR it'll be great so we can see progress, otherwise I will have to unassign the task, as I don't see progress, thanks! |
I will send a draft PR by tonight |
Related to BasedHardware#224 Introduces reminder integration functionality and updates memory creation to include reminder scheduling. - Adds a new `ReminderIntegration` class in `apps/AppWithWearable/lib/backend/reminder_integration.dart` to handle the extraction of reminder details from transcripts and schedule reminders on configured platforms like Google Calendar and Apple Reminders. - Modifies `apps/AppWithWearable/lib/utils/memories.dart` to integrate reminder extraction during memory creation. It now checks transcripts for reminder details and schedules reminders on the user's configured platform if any are found. - Updates `apps/AppWithWearable/lib/backend/database/memory.dart` to include new fields for storing reminder details and the platform used. This allows for storing reminder titles, descriptions, times, and the platform on which the reminder was scheduled.
No relevant progress made. Unassigning. |
Did you know that we have jobs? 😁 and we work on open source on our free time? Maybe next, you should include estimated time to finish the issue. This will help us pick issues we will have enough time to work on :). |
Yes, I understand, but the 2 commits you made, were only after I asked for an update, and you had like 4 days before that. You should've shared some progress within the first 2 days of the task. |
Part 2 and 3 ready in development, comments on part 1 as not sure if that's the right use case. |
Next part of this should be integrate directly with Google calendar. |
A previous PR (discontinued): #230
Correct, not every single action item is worth a calendar or something.
Part 1
Prepare a few keyword phrases
"Hey Friend" Remind me to do X at y time.
During the transcript processing every 30 seconds, it should find if there's this keyword phrase
And, ask GPT to analyze the transcript, and structure the key points, "time" "date" "title", "description" optional.
With that, check which reminders platform the user has configured.
Part 2
During memory creation, it should extract a list of events to be scheduled
generateTitleAndSummaryForMemory
and those should be createdPart 3
Testability of feature.
We create them automatically, or we create drafts of them, so the user includes those events manually to avoid clutter.
It should be easy from the code to change between these 2 options.
Platforms to be configured.
Screens:
So settings should have 2 things, an authorize "Friend" to use calendar and reminders, and one to select which of those to use.
Additionally on onboarding, it should have the option to authorize each of the platforms, or simply skip.
Finally, the memory object should have a events created list, which contain all that data above + platform used, and that should be displayed in the memory_detail page.
NOTE: ideally no backend need, but if so, happy to help.
The text was updated successfully, but these errors were encountered: