[bounty] expose common use case react/nextjs client/server component in screenpipe sdk

[louis030195]

make components that can be installed easily like

import { Video } from "@screenpipe/next"

or

import { useSettings } from "@screenpipe/next"

this one is tricky because it require both client and server code?

or one i have in mind especially: i want the audio player components (video.tsx usually) to have some kind of small button/ui to allow people to assign the voice to specific speaker (like it's done in the identify speaker pipe), this would reduce the friction/effort to identify/name speakers

maybe there are other ones in mind

i think the hard part of this task is to make it easy to export client/server/hooks, etc. nextjs code from the sdk that runs everywhere, so you don't have to export many components (for example i can do the audio one)

overall this task would reduce the effort to create apps on top of screenpipe, better developer experience

/bounty 120

@neo773 wanna tackle this?

[algora-pbc]

💎 $120 bounty • Screenpi.pe

Steps to solve:

1. Start working: Comment /attempt #1088 with your implementation plan
2. Submit work: Create a pull request including /claim #1088 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to mediar-ai/screenpipe!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @neo773	Jan 7, 2025, 12:35:33 AM	WIP
🟢 @itsparser	Jan 7, 2025, 7:09:57 AM	WIP
🟢 @SAIKIRANSURAPALLI	Jan 8, 2025, 11:02:50 AM	WIP

[neo773]

/attempt #1088

Algora profile	Completed bounties	Tech	Active attempts	Options
@neo773	14 mediar-ai bounties + 153 bounties from 27 projects	TypeScript, MDX, Rust & more		Cancel attempt

[itsparser]

/attempt #1088

Options

• Cancel my attempt

[SAIKIRANSURAPALLI]

/attempt #1088

Options

• Cancel my attempt