π³ Tier Price & Benefits:
π Tier 1: Just a Beta β $10 + fee
Beta Access: Guaranteed participation in all beta testing after the Early Beta stage.
Direct Support: Help with troubleshooting issues related to Syrffe Production apps.
Loyalty Rewards: Special perks for long-term supporters.
π Tier 2: Loyal Servant β $20 + fee
Includes all Tier 1 benefits
Development Blog Access: Detailed insights into progress and upcoming updates.
Personal Blog Access: Exclusive posts from me about plans, thoughts, and behind-the-scenes.
Community Voting: Have your voice heard in polls that help shape future updates.
Credits: Your nickname, real name, or X tag featured in the appβs credits (optional).
Early Beta Access: Get access to the latest update 14 days earlier than lower tiers
π Tier 3: Devoted Fan β $30 + fee
Includes all Tier 1 and Tier 2 benefits
Early Beta Access: Get access to the latest update 30 days earlier than lower tiers
If you just want to try the app and enjoy the content, Tier 1 is all you need.
If you want to support the project more deeply, get insider updates, influence the future, and unlock early access, Tier 2 or Tier 3 is your best fit.
π Beta Access Phases
With every new release, access will be reset and redistributed:
The previous beta test will be closed immediately, and access to the old app version will be removed.
A new build will be uploaded, and access will be granted according to your tierβs delay schedule.
π‘ Please note: The app may remain temporarily unavailable for your tier during the scheduled delay period. If this happens, simply wait until the opening date listed in the appβs post description for your tier.
To make access more structured and fair, every update will now roll out in three phases:
Phase 1: Early Beta Access β Tier 3 members
Phase 2 (after 15 days): Access for Tier 2 and higher
Phase 3 (after 30 days): Access for Tier 1 and all paid supporters
π‘ Please note: This approach helps reward every tier β the more you support, the earlier you get access to the newest version.
π Development & Release Cycle
Each new development cycle begins right after every public beta release.
Hereβs what it looks like behind the scenes π
π Month 1 β Full Rest & Recovery
π¬ After each release, Iβm usually completely exhausted, so I take this time to recharge and reset before diving back in. During this month, I also handle access distribution and work on smaller, easier parts of the project.
π Month 2 β Community & Planning
π¬ I run polls, write dev blogs, share updates and ideas, and slowly get back into coding.
π Month 3 β Deep Development
π¬ This month is all about coding. I focus entirely on building the next release and preparing it for testing.
π Month 4+ β Possible Delays
π¬ Any time beyond the third month usually means technical challenges, creative blocks, or real-life circumstances (such as the ongoing war in my country).
π What to Expect
Realistically, new versions shouldnβt be expected earlier than 3 months after a previous release.
My work speed depends heavily on motivation, inspiration, and your support.
π‘ Please note: This project is still a personal passion project, not a full-time studio. Until we grow enough to hire help, please keep that in mind when setting your expectations.