Daily rewards
Bring recurring rewards and their progression context together.
Retention
Give players recurring reasons to return.
A proposed Retention Solution connecting rewards, missions and achievements into a recurring player loop.
An idea under exploration. Scope and timing are undecided.
Is it a fit?
A starting point for your project.
For teams designing daily or recurring activities that connect player goals with rewards and longer-term progress.
Concept — not available
Before you plan around it
Concept. The proposed features still need to be verified together as a complete loop. This page makes no player-retention or revenue guarantee.
Planned product scope
What it aims to bring together.
Candidate capabilities, subject to release verification.
Missions & achievements
Connect player goals, achievements and the rewards attached to them.
Notifications & insight
Coordinate notification and analytics integrations with the planned return loop.
Know the boundaries
Scope & compatibility.
Review the intended installation and the evidence still needed before release.
The complete player loop
Daily Rewards, Missions, Achievements, Progression, Rewards, Notifications and Analytics define candidate scope. A release must demonstrate how these pieces work together.
Provider configuration
Notification, account and analytics providers must be selected and verified for the intended platforms. No supported provider or Unity-version matrix is published yet.
Rules & project adaptation
Mission rules, reward design and notification behavior are project-specific. Custom workflows and integrations require separate scoping.
Product evidence
Demonstrations to come.
Daily Rewards Calendar and Missions and Achievements HUD are candidate demonstrations in the product plan. Verified product footage is not published here yet.
Availability & working together
The product. Help when you need it.
Concept — not available. Scope and timing are undecided. Software licensing and project services are separate offers.
Software · Concept
Retention software license
A proposed Solution license would include its required shared dependencies. Final product inclusion, support terms and a purchase destination are not published yet. Project implementation is a separate engagement.
Ask about the productSeparately scoped services
Aether Retention Integration
Discuss the recurring loop your game needs and the work to adapt its missions, rewards, notifications and analytics. Delivery depends on a defined and verified configuration.
Discuss retention integrationCompare service options & how we work together
Software licensing and project implementation are separate offers. Product-based setup and integration depend on a verified release and supported configuration; a concept page does not establish availability.
How working together works.
Start with a conversation
Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.
Define the work
Where the requirements are uncertain, paid discovery produces findings, risks and a recommended path. Before delivery, we agree on inputs, deliverables, exclusions and acceptance checks.
Build, test and hand over
I deliver against the agreed scope and hand over documentation, test results and known limitations. Ongoing support is a separate agreement.
A direct line to the developer
Tell me what you're building.
Interested in the Retention concept? Describe the problem you'd want it to solve. This is an expression of interest, not a preorder or a release commitment.
