How we build our apps

Last updated: October 20, 2026

This page describes the standards Cornelia Cove LLC follows when it designs, builds, tests, releases and supports its apps. It is our editorial and engineering policy in plain language. If we change how we work in a way that affects you, we will update this page and the date above.

1. Start from one job

Every app begins with a single, specific job the software should do well, written down in one sentence before any design work starts. For Calla: Vision Board & Widgets, that job is helping people build a vision board and keep it in view during the day. Features that do not serve the core job are left out of the first release, even when they would be easy to add. We would rather ship something small and dependable than something broad and fragile.

2. Collect the minimum

Before a feature is built we ask what data it needs and where that data will live. Our default answers are "as little as possible" and "on the person's own device". Concretely, that means:

Any exception, such as the purchase validation described below, must be listed in our privacy policy before it ships.

3. Prefer Apple's frameworks

We write our apps natively in Swift and use Apple's system frameworks for interface, storage, widgets, notifications and purchases wherever they cover the need. Each third-party dependency is reviewed for what data it receives and whether a system framework could do the same job. Today the one third-party service in our purchase flow is RevenueCat, which validates App Store purchases and manages subscription status. It receives an anonymous identifier and purchase history, never your name, email address or content.

4. Honest pricing

Paid upgrades are optional, and the free version of an app must remain useful on its own. Prices are shown in the app before you confirm anything, and subscription terms, including trial length and how to cancel, are stated on the upgrade screen and in our terms of use. We do not use countdown timers, fake discounts or pre-checked boxes, and every upgrade screen includes a working "Restore purchases" option. Refunds are handled by Apple through its own process.

5. Testing before release

Each release is tested on physical devices as well as in simulators. Our pre-release checklist covers:

A release does not ship while a known crash, data-loss bug or broken purchase path is open.

6. Releases and review

Apps reach people through Apple's App Store, so every version also passes Apple's App Review. We write release notes that say what actually changed, in plain words, instead of a generic "bug fixes and improvements". When a change affects privacy, pricing or how data is stored, the release notes say so directly and this site is updated in the same week.

7. Support and corrections

Support email goes to the people who build the apps. We aim to answer within two business days, and every reproducible bug report is logged and tracked until it is fixed or explained. If a reader finds a mistake on this website, on one of our free web tools, or in an app's text, we correct it and update the page date. Our free web tools follow the same rule and list the public documents their figures come from on their own methodology and source pages.

8. Writing standards

Text on this site and in our apps is written and reviewed by people at the studio. We avoid claims we cannot support, such as promised outcomes from a motivational app, and our apps are not a substitute for professional, medical or financial advice. We do not publish testimonials, ratings or download counts unless they come from a source you can check.

9. Who is accountable

Cornelia Cove LLC is responsible for everything published under its name. You can reach us at hello@corneliacove.com for general questions, support@corneliacove.com for app help, or privacy@corneliacove.com for privacy requests. More about the studio is on our about page.