Renew
Taking a recurring schedule and payment manager from idea to App Store release.
Renew is a mobile app for managing subscriptions, recurring schedules, and payment dates in one place. I handled product definition, design, development, testing, and release.
Renew
Overview
The problem
Subscriptions, recurring tasks, and payment dates are easy to lose across separate calendars, reminders, and account screens.
What shipped
I defined a focused mobile product, built its core schedule and notification flows, implemented in-app purchase, and completed App Store review and updates.
One place for recurring obligations
Renew began as a way to see subscriptions, repeating schedules, and upcoming payments together. I set the product boundary around recurring items, upcoming dates, calendar context, notifications, and exchange-rate reference rather than turning it into a broad finance or task-management product.
Building the full release path
- 01
Defined the product scope and information architecture around recurring items and upcoming obligations.
- 02
Designed the core mobile flows, interface states, calendar views, and notification logic.
- 03
Developed and tested the app, fixed release issues, and configured in-app purchase.
- 04
Completed App Store review and continued with release updates.
Verified release scope
- Distribution
- Released on the App Store
- Commerce
- In-app purchase configured
- Product work
- Scope, information architecture, UX and UI
- Delivery
- Development, testing, review, and updates
What end-to-end ownership changed
Owning the whole path made trade-offs immediate. Information architecture affected data structures, notification decisions affected permissions and edge cases, and interaction polish had to survive real implementation and review requirements. The project strengthened my ability to design within delivery constraints without using unverified adoption numbers as a substitute for learning.