←
Cornelius Mark25,521 posts
Cornelius Mark avatar

Cornelius Mark

@corneliusmark

Innovative macOS/iOS developer building apps that shine. Need a bold app solution? DM me let’s create! ⬇️

◷ Joined December 2010▧ 2,734 Photos and videos
Cornelius Mark avatar
Cornelius Mark@corneliusmark·5 Jun 2025

Hello, I craft macOS and iOS apps that scale, perform, and delight users. From modular architectures to bug-free code, I deliver solutions that grow with your vision. Let’s chat about your next project! Here’s what clients say about my work: ⭐⭐⭐⭐⭐ "Mark is a guru in everything MacOS and app store related. A pleasure to work with!" – Safari extension for a search engine. ⭐⭐⭐⭐⭐ "Great communication, fluent English, quick action, knows exactly what he's doing." – macOS taskbar app. ⭐⭐⭐⭐⭐ "Mark was great to work with and is an expert at his craft." – WidgetKit widgets for Big Sur. DM me let's build something amazing! Best, Mark

Cornelius Mark avatar
Cornelius Mark@corneliusmark·Sep 29

Put Basic, Plus, and Pro on one screen. Keep Plus as the plan you can live on. Then count which button gets pressed for two weeks. If almost nobody picks Plus, the mid plan is still too thin or still too high. Fix that. Do not hide Pro because it feels loud.

Cornelius Mark avatar
Cornelius Mark@corneliusmark·Sep 29

Make Pro real. More projects. Longer history. Shared access. The thing a heavy user actually hits. Fake locks get screenshotted.

Cornelius Mark avatar
Cornelius Mark@corneliusmark·Sep 29

Add a high Pro tier. Not as a joke plan. As the expensive neighbor. Plus suddenly looks like the plan a serious person picks.

Cornelius Mark avatar
Cornelius Mark@corneliusmark·Sep 29

One cheap yearly price looks humble. It also tells people the product is small. Small products get treated like extras.

Cornelius Mark avatar
Cornelius Mark@corneliusmark·Sep 29

A full week of cheap jobs can still leave you short. Look at the bottom fifth. Lowest ticket. Most extras. Most arguing about the bill. Those names keep the phone busy. They also block the jobs that would have paid for the van. Drop that slice and the diary can look quieter. The week can still earn more. Friday is no longer a cleanup day. Busy is not the same as paid.

Post attachment
Cornelius Mark avatar
Cornelius Mark@corneliusmark·Sep 29

You did not run an experiment last week. You ran a release. Three retention ideas went out together. A shorter onboarding. A new reminder. A paywall with different copy. Day 7 ticked up two points. The Slack thread called it a win. Nobody can say which change earned the two points, or if the cohort was just a better week of traffic. Retention tests fail in two quiet ways. Too many changes at once. And reading the chart before the cohort finished its cycle. The people who installed on Monday have not lived with the product long enough by Wednesday. Their day 1 is not their day 7. Their day 7 is not their day 30. Pick one major change. Freeze the rest. Hold the line until that install group reaches the day you actually care about. Then decide: keep it, revert it, or run the next test. If you cannot point to one change and one cohort, you do not have a result. You have a story about a busy week.

Post attachmentPost attachmentPost attachmentPost attachment