Frontend: Saved Stream Templates

[ogazboiz]

Summary

Allow users to save common stream configurations as templates.

Motivation

Reduces friction for recurring payment setups with similar parameters.

Tasks

• Add UI to save current create stream form as a template.
• Persist templates locally or via backend.
• Allow selecting a template to prefill the form.

Acceptance Criteria

• Users can create, edit, and delete templates.
• Creating from a template still allows overrides before submission.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Favourof]

@Favourof has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Enable users to save their frequently used stream setups as templates, making it faster and easier to create recurring streams with similar parameters.

Why it matters:
Users often create multiple streams with the same settings. Templates reduce repetitive input and streamline the workflow.

Proposed Solution:

Add a UI option to save the current “Create Stream” form as a template.

Persist templates either locally (browser storage) or via the backend.

Allow users to select a saved template to prefill the form when creating a new stream.

Ensure users can override template values before submitting.

Acceptance Criteria:

Users can create, edit, and delete templates.

Using a template pre-fills the form but still allows edits before submission.

Templates persist reliably and improve the user workflow.

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

[drips-wave]

Congratulations, @Favourof! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Favourof: 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 issued 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 🌊

[drips-wave]

This issue has been completed by @Favourof as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @Favourof: 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.