[Frontend] Content routes are client components with no per-route metadata - every page shares the root title/description

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

All content routes start with use client (activity/page.tsx, incoming/page.tsx, settings/page.tsx, streams/create/page.tsx, streams/[id]/page.tsx), so none can export const metadata. The only metadata is the root one, meaning /activity, /settings, /streams/create, etc. all emit the identical title FlowFi | Real-time Payment Streams.

Acceptance criteria

• Give each route a unique title/description by moving the use client logic into a child component and keeping page.tsx as a server component exporting metadata (or generateMetadata for /streams/[id])
• Verify /activity, /settings, /streams/create and /incoming each render a distinct title

Files to touch

• frontend/src/app/activity/page.tsx
• frontend/src/app/settings/page.tsx
• frontend/src/app/incoming/page.tsx
• frontend/src/app/streams/create/page.tsx
• frontend/src/app/streams/[id]/page.tsx

Out of scope

• Indexing gated/authenticated pages
• robots/sitemap (tracked separately)

[Oluwasuyi-Oluwatimilehin-Daniel]

@Oluwasuyi-Timilehin has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello @maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately. And I will deliver at the shortest possible time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Timilehin to this issue.

[razeprasine]

@razeprasine has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer, I’d like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @razeprasine to this issue.

[grantfox-oss]

🦊 GrantFox — @razeprasine has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #874)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @razeprasine! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @razeprasine: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@razeprasine's PR #930 was approved and merged by @ogazboiz.

🏆 @razeprasine: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (503 total points). Track your full progress on GrantFox.

👏 Great work, @razeprasine! Keep contributing to LabsCrypt.

[drips-wave]

This issue has been completed by @razeprasine as part of the Stellar Wave Program's 6th Wave 🥳

😎 @razeprasine: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.