OMP · Online Marketing Platform

A notification app per organization.

Scanning a QR code is the whole sign-up: pick the topics you want and notices arrive on the lock screen. Delivery is web push, so sending costs nothing per message.

The site asks for an access code. Real organization logos are used, so it is kept out of public reach and out of search.

One platform, an app per organization. Each gets its own address, app name, icon color, topic list and admin screen. Adding one is a form, not a release.

Design

Three decisions that shaped it

Organizations already have a way to reach members: paid message channels. The question was what a notification service can offer instead, and what it has to give up to do so.

A web app in place of a native appNo developer account per organization and no yearly rebuild of one app per client. Delivery is web push, which carries no per-message fee. The cost is the first step on iPhones, where notifications require the page to be added to the home screen first.
No identifying dataAge band, region, topics and the consent record. No name, no phone number, no email, no account. Targeting runs on what the member chose at sign-up, and the device token is stored only as a hash.
Compliance is not left to the operatorThe ad label, the night sending limit, the opt-out path and the two-year re-consent count are applied automatically when a message is sent, rather than being rules someone has to remember.
What it does

Scan the QR, choose, receive

Four steps, two on the member's side and two on the organization's.

Scan the QR and joinThe QR code on a poster or a receipt opens the organization's own app. Pick the topics, set the age band and region if you want, and agree separately to marketing messages and to night-time messages. No name, no phone number.
Turn notifications onOne tap subscribes the browser to web push. On Android Chrome, allowing it there is the whole step. On iPhones the page has to be added to the home screen first and opened from that icon, and the app explains where the share button is for each browser.
Write a noticeCards carry an image, a title, body text and one button. The audience is a combination of what members chose at sign-up, and the admin screen shows how many people that reaches before anything is sent.
Send and read the resultThe notice arrives on the lock screen; tapping it opens the cards. Delivery, open and button clicks are recorded per member, so a notice can be read by recipient and a member by the notices they received.

Members without notifications still get the message. Anyone who declined or has not enabled push finds the same notice in the in-app inbox.

Compliance

What is applied automatically at send time

Korean law treats a push notification as an electronic advertising message. These rules are applied when a message is queued rather than left to the operator.

Rule What the code does
Ad labelMessages marked as advertising get the label prepended to the title, once, at send time
Consent scopeAdvertising reaches only members who consented to it; notices reach everyone matching the audience
Night holdBetween 21:00 and 08:00, advertising goes out immediately only to members who consented to night messages; the rest is held until 08:00
Opt-outEvery advertising message carries the opt-out path, and a member who opts out while a message is held is dropped from that send
Two-year re-consentMembers whose consent is approaching two years old are counted on the admin dashboard
Data keptAge band, region, topics, consent timestamps and the push subscription. The device token is stored as a hash

Withdrawal is checked at delivery, not at scheduling. A held message re-reads consent the moment it is finally sent.

Operations

Run by planning, not by deployment

Everything an organization needs day to day is in the admin screen, so the work does not queue behind an engineer.

Three roles, three screensThe platform operator registers organizations and sees usage across all of them. Each organization gets its own admin screen with its own password, reaching only its own members. Subscribers see neither. Requests run the other way too: an organization asks the operator from its own screen and reads the answer there.
Web push is the floor, paid channels are optionalWeb push costs nothing per message and is always on for every organization. KakaoTalk, SMS and email can be switched on per organization when a notice has to reach people who never enabled notifications, and those carry a per-message fee the organization agrees to. Plans differ in how large a notice may be rather than in what the product does.
Adding an organization is a formApp name, sending organization, address, brand color, logo and topic list. Submitting it creates the member app, the admin screen, the colored app icon, a printable QR poster and one sample notice. No code change, no deployment.
Topics and regions stay editableRenaming a region moves the members already recorded under it, and a renamed topic keeps its internal id so existing members stay in the audience. Deleted entries leave the member record intact and only disappear from targeting.
Archive before deleteArchiving stops new sign-ups and sending and hides the organization from the public list while keeping every record. Deletion is available only after archiving and requires typing the address back.
Separate per organizationMembers, notices, delivery history and images belong to one organization, and the admin screen acts on the organization it is opened for. Regression tests cover the isolation along with the send rules.
Limits

What this does not claim

The economics are settled; reach is the open question.

Not a replacement for a messengerA messenger is already on the phone. Here the first step is a scan and, on iPhones, adding the app to the home screen. How many people complete that is the number the model depends on, and it has not been measured at scale.
One more step on iPhonesAndroid Chrome subscribes from the page itself, but web push on iOS requires the page to be added to the home screen and opened from that icon, on iOS 16.4 or later. A home-screen app also has its own storage, so the sign-up is done there rather than carried over from the browser.
The notification is a headline, not the messageA push carries a title, a line of body text and at most one image. The cards open after the tap, which is one step more than a message that arrives fully expanded.
A fallback costs more than moneyMembers who never enabled notifications are reached only through the in-app inbox. A paid channel can be switched on to reach them, but KakaoTalk, SMS and email all need a phone number or an address — and not collecting those is what keeps this service simple to adopt. Turning one on changes what the organization holds, not just what it pays.
A demonstration, not a live serviceThe organizations shown are demonstration tenants, the sample notices are fictional, and the demonstration site is behind an access code. Nothing here is an official service of those organizations.