Product & iOS engineering
Two people. App design, Swift, the shared SDK, release engineering and the parts of the ad stack that decide when a placement may load.
About the company
Applaud Ads Limited builds and operates iOS utility apps from Hong Kong. The team is four people. The product line is three apps. The plan is to keep both numbers modest and the work careful.
We make small tools for people who work with mobile apps, and we pay for them with advertising. That is the whole business. There is no network to join, no agency retainer, no dashboard sold to other publishers.
The apps come first. BannerGuard checks ad layouts before release. AdLens keeps ad revenue numbers readable without a spreadsheet. RetentionKit tracks a few retention checkpoints without a data warehouse. Each one solves a problem we kept running into ourselves.
The ad stack is ours as well: mediation between Google AdMob and Meta Audience Network, frequency caps per app, consent handling, and reporting at placement level. We built it in-house because it is the only way to explain where the money and the data actually go.
Why Hong Kong
Hong Kong is where the company is incorporated, where its records sit, and where the office is. It is also a sensible time zone for working with ad partners and app platforms that operate across Asia and the United States.
We do not claim to be a global operation. The company is registered in Tsim Sha Tsui; the work happens wherever the laptop is open. Being explicit about that is more useful to a reviewer, a partner or a customer than a map full of pins.
History
Short version: one test app, one shipped tool, then the parts needed to run both properly.
Applaud Ads Limited is registered. The first internal ad stack is written against a single test app, mostly to learn what the mediation layer could and could not report.
The first public app. It started as a checklist for banner ads that overlapped safe areas and tap targets in our own builds, and became a standalone checker.
Google AdMob and Meta Audience Network are integrated through our own mediation layer. Reporting moves from blended totals to placement-level numbers.
A pocket dashboard for daily impressions, revenue, eCPM and ARPDAU. Built from the spreadsheets we were keeping by hand; the numbers stay on the phone.
Cohort checkpoints for D1, D7 and D30, compared release over release, without a warehouse. Closed beta by email request.
The team
We do not publish stock headshots or invented executive titles. This is how the work is divided, and everyone — including the person reading this — can be reached at the same address.
Two people. App design, Swift, the shared SDK, release engineering and the parts of the ad stack that decide when a placement may load.
One person. Interface design, accessibility checks, device testing and the unglamorous pass that happens before anything goes to review.
One person. Mediation settings, ad partner relationships, placement reports and the weekly look at whether the numbers mean anything.
Shared across the four of us. Privacy requests, App Store review questions and the inbox that starts with admin@.
Principles
None of these are unusual. They are written down so that growth pressure has something to push against.
We would rather maintain one app that survives a year than ship five that get deleted in a week. New products have to earn their place in the line.
Frequency caps are set per app, not per revenue target. No forced video, no fake close buttons, no ads that imitate the interface.
No accounts, no contact lists, no precise location. Advertising identifiers are handled per vendor and only where the platform permits it.
Every third-party SDK is reviewed before it ships: what it collects, when it starts, and what happens when a user declines tracking.
Where we are
Our registered address is in Tsim Sha Tsui, Kowloon. Questions about the company, privacy or a specific app can go to the same inbox.
Next
Company, product or privacy questions all reach the same small inbox. We answer within two business days, Hong Kong time.