Last Week

Last week was the milestone I had been waiting on: Shokken finally cleared Apple’s App Store review. Android was already live on Google Play, but iOS had been stuck behind repeated review rejections around the short-duration paid access products. After deleting the old one-day and three-day product records from App Store Connect, the review path finally cleared.

That approval changes the shape of the work. The MVP development effort is effectively done. Google has approved the Android app. Apple has approved the iOS submission. I still need to publish the iOS app, but the major platform gate is no longer the blocker.

So this week moved into a different mode: marketing preparation. Not advertising yet. Not a polished launch campaign yet. The work right now is building all the surfaces that make Shokken look real, trustworthy, useful, and ready for someone outside my development bubble to evaluate.

The Product Exists. Now It Needs To Look Real.

This week was about marketing prep.

That phrase sounds smaller than the work actually is. I am not just writing a tagline and calling it done. There are multiple surfaces that need to line up before I start asking restaurants and operators to take Shokken seriously:

  • physical one-pagers for in-person visits
  • website assets
  • search presence
  • Google business presence
  • app store listings
  • screenshots
  • social profiles
  • short-form video channels
  • launch and outreach targets

Each of those surfaces sends a trust signal. A restaurant owner who sees a flyer, scans a QR code, lands on the website, searches the company name, opens the app listing, and checks social media should not feel like they are stepping into an abandoned side project. The product needs to look maintained, supported, and coherent.

That is the work now.

The most tangible piece this week was the physical flyer. I have been iterating through versions of a one-page handout that I can take into restaurants. The flyer needs to explain what Shokken does quickly, show the app clearly, include a value proposition, and give the recipient a way to try it immediately. The current version includes a “test it yourself” QR code, pricing information, and a link back to the website.

I have only been printing prototypes on regular paper so far. Before committing to a design, I wanted to see layout, margins, text density, and whether the screenshots were legible. The next step is printing on heavier cardstock with a higher-quality inkjet printer. If that still does not look good enough, I may need to use a commercial printer.

The less visible work is just as important. I submitted the site information so Google can index it properly, registered the business presence where appropriate, and started setting up social profiles with tailored bios, banners, and profile assets. YouTube, LinkedIn, X/Twitter, Instagram, and TikTok are in motion. Facebook has been less cooperative, but it matters enough for the target audience that I still need to solve it.

This is not glamorous work. A lot of it ends with a blank page that merely looks ready. But that readiness matters. It is the difference between a product that technically exists and a product someone might trust.

What does it mean in English?

The app is no longer the only thing that needs to be built.

Now that Shokken is approved on both platforms, people need to be able to discover it, understand it, and trust it. That means the website, app store listings, screenshots, social profiles, flyers, and demo videos all matter.

If someone hears about Shokken and searches for it, they should find a real business, not a confusing empty trail. If a restaurant owner scans a flyer, the page they land on should explain the product clearly. If someone opens the App Store listing, the screenshots should sell the value instead of just proving the app has screens.

This kind of work does not feel like coding. There is no build button and no immediate feature to play with. But it is still product work. Without it, the app can be technically ready and still fail to reach anyone.

Nerdy Details

The flyer is a sales surface, not documentation

The first marketing surface is physical.

My plan includes visiting local restaurants directly, which means I need something to hand to a person. That piece of paper has to do several jobs at once.

It has to make Shokken understandable in a few seconds. It has to look professional enough that the recipient does not immediately dismiss it. It has to show that the app is real. It has to give them a next action, ideally one that does not require a long conversation while they are busy running service.

That is why the QR code matters. A “test it yourself” QR code lets someone experience the guest side quickly. They can scan, see the waitlist flow, and understand the shape of the product without trusting my explanation alone.

The back side carries more supporting information: pricing, website, and enough detail to make the handout useful after I leave. The flyer is not meant to be the whole sales process. It is a bridge from a short in-person interaction to a more complete product evaluation.

The design process has been iterative. I have gone through several versions, printed them on ordinary paper, checked legibility, adjusted screenshots, and refined the hierarchy. That is cheap and fast, which is what I want before spending money on better paper or professional printing.

The next test is production quality. The heavy cardstock should make the handout feel more deliberate. The printer matters too. A laser print made the dark app screenshots muddy, so I want to test a higher-quality inkjet before deciding whether to outsource printing.

The goal is not luxury. The goal is credibility.

Search presence is part of trust

The next surface is search.

If someone hears “Shokken” and searches for it, the result should not look empty. Ideally, they should find the website, the app listings, and a business profile that confirms this is a real product with a real operator behind it.

This is not the old caricature of SEO where every page is stuffed with keywords and tricks. The useful work now is much more basic: make sure Google can find the site, understand what it represents, and associate it with the right business entity.

That means submitting the site through the right Google tooling, making sure the metadata is coherent, and registering the business presence without exposing a personal address. Shokken is a software service, not a storefront, but it still benefits from appearing as a recognizable entity.

That matters because trust is cumulative. A Google business result does not prove that an app is good. A social profile does not prove the product is maintained. A professional flyer does not prove the backend is reliable. But each one is a data point.

When all of those data points agree, the product feels less risky.

That is especially important for Shokken because the app asks a business to put operational workflow and guest communication through a new system. A restaurant operator has every reason to ask whether the product will still be supported next month. Search presence and business identity do not answer that completely, but they reduce the sense that the product appeared from nowhere.

App store screenshots are conversion assets

The app store listing is another major surface.

The screenshots I used during review were mostly submission assets. They satisfied the requirement. They showed that the app had screens. They were not designed as sales material.

That is not enough anymore.

A real app store listing has to argue for the product quickly. Popular apps do not just dump screenshots of raw UI. They use screenshots as a short story: what problem does this solve, what does the app feel like, and why should the user install it?

For Shokken, that means the screenshots need to communicate the waitlist workflow clearly:

  • guests join from a QR code
  • hosts manage the queue
  • parties can be called or updated
  • notifications reduce host-stand friction
  • paid access unlocks the operational features that matter

The screenshots need captions, context, and visual polish. They need to look like someone cared about the listing, because the listing is part of the product’s first impression.

This is where a lot of conversion loss happens. A potential user may discover the app, open the listing, glance at the screenshots, and decide in a few seconds whether it feels worth trying. If the screenshots look like placeholders, that decision can be lost before the user ever installs anything.

So the app store asset refresh is one of the next concrete tasks.

Social profiles are both channels and proof of life

Social media has two jobs.

The obvious job is distribution. Each platform is another channel where someone might encounter Shokken: X/Twitter, Instagram, TikTok, LinkedIn, YouTube, Facebook, and whatever else turns out to matter for restaurant operators.

The less obvious job is proof of life.

If someone searches for Shokken and finds no social presence at all, the product can feel thin. A blank or missing profile raises questions: is this maintained, is there support, is this a real business, is anyone listening?

That does not mean every platform needs a high-volume content machine immediately. In fact, setting the cadence too high would be a mistake. I do not want to build a schedule that burns me out before I learn which channels matter.

The first step is simpler: claim the profiles, make them look intentional, write platform-appropriate bios, add banners and images at the correct sizes, and link them back to the product. That creates a baseline presence.

After that, I can start with a low posting cadence and increase only if the workflow proves sustainable. The goal is to learn which messages work without turning social posting into another full-time product.

Facebook is the current rough edge. It should matter for this audience, because many local business and restaurant communities still use Facebook heavily. But page creation has been failing with unhelpful errors. That is not a product blocker, but it is one more reminder that marketing infrastructure has its own weird operational friction.

The website has moved from placeholder to product surface

The website also needed a refresh.

The missing video section now has a video. It does not have audio, but it gives a short visual explanation of what the app does. That is already an improvement over a blank or promised section.

The website is important because it is the hub all the other surfaces point back to. The flyer points there. The app store listing can point there. Social profiles point there. Search results point there. If the website is weak, every other channel inherits that weakness.

The website needs to answer the same questions as the flyer, but with more room:

  • What is Shokken?
  • Who is it for?
  • What problem does it solve?
  • How does a guest join?
  • What does the host do?
  • What does it cost?
  • How do I try it?

The site does not need to be overdesigned. It needs to be clear, current, and specific. It should show enough of the app to make the product concrete and enough of the workflow to make the value obvious.

That is why the video matters. A short visual flow can explain more quickly than a paragraph. Even without audio, a product walkthrough can make the app feel real.

Marketing prep has delayed feedback

One of the harder parts of this work is the lack of immediate feedback.

When I implement a feature, I can build the app and use it. When I fix a backend issue, I can run a test or inspect the behavior. When I improve CI, I can watch a job pass.

Marketing prep does not feel like that.

Creating a social profile, writing a bio, making a banner, submitting site metadata, or iterating on a flyer often ends with something that is simply ready. Nothing dramatic happens. There is no immediate user, no install spike, no obvious validation.

But readiness is still valuable.

The point of this week was not to generate demand instantly. It was to remove the obvious trust gaps before outreach begins. When I start showing up at restaurants or posting short-form content, I want the supporting surfaces to already be in place.

That way, if someone does take the next step, they land in a coherent product story instead of a half-finished trail.

The work is shifting from development to business

The larger shift is that Shokken is moving from development mode into product and business mode.

That does not mean engineering is over. There will be more product work, more bugs, more platform issues, and probably more billing decisions. But the center of gravity has changed.

For most of this project, the hard question was whether I could build and ship the app. Now the hard question is whether I can get people to care.

That requires different skills: positioning, messaging, outreach, visual polish, channel strategy, follow-up, and patience with a kind of work that has much slower feedback than code.

It is new territory for me, but it is also the correct next phase. A product that nobody discovers is not meaningfully shipped. The app stores are nearly in place. The website is improving. The print material is getting closer. The social surfaces are being claimed.

Now the project has to leave the development cave and meet actual operators.

Next Week

Next week is about finishing the launch surfaces.

I need to complete the app store listing refresh, including better screenshots and supporting assets. I also need to validate the final flyer print quality, decide whether home printing is good enough or a commercial printer is necessary, and keep tightening the social profiles.

After that comes the real outreach: showing up at local restaurants, publishing short-form content, and exploring launch channels like Product Hunt and industry-specific groups such as restaurant associations.