When Search Console finds a traffic asset
Separate impressions, product use and revenue before turning a surprising traffic number into a business plan.
This is the running log of turning small Mac and iPhone apps into useful conversations. Each entry has a job, a channel, a measurement, and a next decision. The misses stay in the record.
Separate impressions, product use and revenue before turning a surprising traffic number into a business plan.
257 pageviews, one settled purchase, and the next distribution loop for turning attention into app revenue.
Search Console decisions, Tinylytics baselines, controlled changes, and the next check.
Choose one page, make one change, and measure the next 100 visits without waiting for a big audience.
What changed when the product page made the buying step too indirect.
Separate discovery from conversion and choose one narrow intent experiment.
Turn one release into a useful explanation, a proof asset, and a measurable distribution test.
Fix the path between a live App Store release and the site that should send people to it.
Answer real questions first and earn the right to share a deeper workflow later.
Put a focused product where its buyers already look, then count qualified visits and sales—not submissions.
How a release becomes a small experiment instead of disappearing into the store.
Turn the Mac App Store pre-flight check and platform comparison into a clear launch entry point.
Why building from Japan, supporting customers directly, and documenting the work changes the product.
Concrete workflows and results from using the tools on our own launches and site.
Turn a report into one page, one decision, and one measured follow-up.
Use user language, screenshot clarity, and controlled listing changes before buying another suite.
A practical sequence for the page, metadata, proof, and first distribution actions.
Older experiments, decisions, and field notes from building the studio.