Mobile app · Product development

Building Priora from Beta Testing to Google Play

Priora is where my long project-management background became a hands-on product: a focused weekly planner refined through real beta feedback and release work.

Building Priora from Beta Testing to Google Play
Project image from WynnWorld.

A productivity app shaped by project-management habits

Priora came from a problem I understood personally: a task list can become another place to collect work instead of helping decide what deserves attention today. After more than twenty years in program and project management, prioritisation, follow-up and keeping work visible were already familiar parts of my professional life.

When I began building my own digital products after leaving corporate work, I wanted to translate some of those habits into a smaller personal tool rather than recreate a full enterprise project-management system.

The core idea: a weekly planner with a Daily Top 3

Priora is organised around a weekly view and a Daily Top 3 focus. The intention is to keep the most important work visible instead of treating every task as equally urgent. During testing, this focus mechanism also needed rules so completed items did not block the user from choosing what mattered next.

That led to the smarter focus behaviour introduced in version 1.0.1, where completed focus tasks can automatically release their slot. It is a small feature, but it came directly from the way people actually used the app.

Testing with real people

Before public production, Priora had fourteen beta testers. The test plan covered sign-in, task creation and editing, reminders, voice-to-text, dark mode, new-week creation and the paid-tier flow. Testers were given access to the Pro features so the goal was to test the experience rather than payment friction.

The feedback was useful because it exposed problems that were easy to miss while developing. The home screen had too much blank space. The focus behaviour felt limiting once tasks were completed. Some settings needed to persist more reliably. These are exactly the kinds of issues that do not always appear in a feature checklist.

What changed in version 1.0.1

The first significant update included smarter focus behaviour, a more compact dashboard, faster navigation, task-edit fixes, improved voice-to-text, reminder permission handling, saved week-start preferences, week-creation fixes and purchase restoration support.

The lesson was that the app did not need more features first. It needed the existing workflow to feel more dependable.

Preparing for Google Play

Publishing a mobile app also introduced work that had nothing to do with the main task planner screen. Store assets, policy pages, data-safety declarations, account data deletion, legal links and pricing all had to be reviewed.

Version 1.0.2 updated the fallback Pro pricing, legal endpoints and the permanent account-data deletion URL, and refreshed store assets. The data-deletion policy was also changed to state that deletion is immediate and permanent rather than retaining an earlier seven-day period.

Why this belongs on WynnWorld

Priora is different from the music and browser-game projects, but it reflects the same broader transition behind WynnWorld. After a long corporate career and a layoff, I started teaching myself newer AI-assisted tools and building products directly. Priora is where my project-management background and hands-on product development meet most clearly.

It is also a reminder that a small app still needs product thinking, testing, policy work, release discipline and user feedback. Writing those decisions down gives the project more value than simply linking to a store page.

What I learned

The most useful lesson was that real users notice friction before they care about feature count. A compact dashboard, reliable editing and understandable focus behaviour can matter more than adding another advanced function. That is why I now treat feedback, release notes and policy maintenance as part of the product rather than separate administration.

Continue exploring

Open Priora →View the Priora project page →