No more month-end surprises
Snap a receipt and today's spending becomes one line. The month view shows it all at a glance.
Say you've opened a lovely shop on an island. The goods are good and you fitted it out with care. But there's no ferry. What happens? Nobody knows the island exists. An app is the same. Being listed in the store only means you built the shop. For people to notice the island and step aboard, boats have to come and go steadily, at set times.
Why you need boats
The store is a wide harbour, but people search only for apps whose names they already know. An app nobody has heard of is a boat moored somewhere in the harbour, out of sight.
So you have to tell people about the island from outside it. One post is one boat on the sea lane, catching an eye with “there's a shop over there.”
- The islandYour app
- The landingYour store or intro-page link
- One boatOne post
- The timetableA steady posting rhythm
People feel an island with frequent boats is alive. Two apps side by side, one last heard from six months ago and one with news this week: which do you tap?
What to load on the boat
There's already plenty to load inside your app. Just don't use the feature's name; use the words of the moment someone opens it.
One screen, one story
Pick a screen and say in one line when someone uses it. It reads far better than a feature list.
Updates, in your customer's words
Turn the release notes into what got easier. Keep the version number inside the app.
Use it when…
Draw the moment they reach for the app: the commute, before shopping. Remember the moment and they remember the app.
How it was made
Why you added a feature, what you took out. The maker's voice builds trust.
A small tip
One feature people don't know about. The kind of post they save.
A user's line
Turn a review into a clean card, with permission. It outlasts anything the maker says.
New: recurring costs
Enter rent and subscriptions once. You won't have to retype them every month.
Use it before you shop
Three minutes outside the supermarket to check what's left for the week. The cart feels easier to fill.
Sample posts · not real shops or services
If you're thinking…
Two things app makers say most often.
“My app is hard to explain”
The harder it is, the more you cut it into single screens. We read your intro page and turn each feature into who uses it, and when.
“I don't have time for screen recordings”
That's fine. A few screenshots and a sentence make a post. We use the images you upload first.
Boats on a timetable
Two or three posts a week is enough: a feature on Tuesday, “use it when…” on Thursday, and one extra update story the week a new version ships.
The days are an example; move them to fit your work. That boats on a fixed timetable are easier to remember is a rule of thumb, not a guarantee.
The common mistake
The one we see most often.
What Meok does
From one link we read what the app does, who uses it and how it sounds. Then:
It reads your app from the linkGive us the store or intro page and we read the features, the people who use them and the tone.
It turns features into storiesWe turn the feature list into “when you'd use it” and spread it across a month of posts.
Your images come firstUpload screenshots or promo images and we use them first.
No invented numbersDownloads, ratings, discounts: we don't write numbers that aren't confirmed.
You chooseRight if you like it, left if not. To change something, just say so in words.
Keep building the app. We'll lay out the sea lane.
