You are here: 03 / About

ABOUT / The maker

The person you first talk to stays on after launch.

I started at Samsung SDS and moved through enterprise systems, games and large-scale backends. Today I build apps and websites myself, from first sketch to release.

PROFILE

Founder & developer, LAONMON

LAONMON is a one-person studio. The person who takes your enquiry, writes the scope document, designs and codes, ships to the stores and handles fixes after launch is me.

See the case studies
Years in software
29years
Enterprise systems to games, servers and apps, client and server alike
Apps shipped
4apps
Released on the App Store and Google Play, and I still run them
Site languages
3languages
Korean · English · Japanese

CAREER

What I've done

  1. 01

    Enterprise systems — from analysis and design

    At Samsung SDS I analyzed, designed and built enterprise systems — linking air cargo logistics with RFID and automated ski-resort gates, where on-site hardware and software had to work together — and wrote proposals. Before that, I developed SI projects for public-sector organizations and associations.

  2. 02

    Games — server and client

    I developed both the server and the client for two mobile games: lockstep synchronization that keeps two devices in step during real-time battles, the battle client, and the overall architecture (MVVM, ECS).

  3. 03

    Backends at scale, and running them

    I designed and built microservice backends and ran them in production on Kubernetes — a reactive stack (WebFlux, Kafka, Redis), database redundancy, JWT authentication and deployment automation. One was the server for an education service whose curriculum adapts to each learner's level.

  4. 04

    Real-time communication, security and 3D

    WebRTC video calls, end-to-end encrypted chat, and Unity-based 3D data visualization.

  5. 05 / NOW

    Now — apps and websites, idea to release (LAONMON)

    I've taken four apps from planning to release on both app stores and still run them. I also built and run this trilingual site and an AI assistant that runs on my own server.

    See the case studies
    The laonmon.com English home page on desktop and phone

SOLO STUDIO

I work alone, so let me say that up front.

LAONMON has no employees. Before hiring me, it's fair to wonder: what happens if I get sick or become unreachable? So I work in a way that makes that worry smaller from day one.

  • Domains, servers and app developer accounts are created in your name from the start, and billed to your own account. Nothing sits in my account.
  • So whatever happens, your site, your app and their accounts stay in your hands.

Working alone has upsides too: nothing gets lost passing between people, and when you ask a question, the person who built it answers. The trade-off is that I can't take on many projects at once, so we agree start and finish dates during consultation.

OWN PRODUCTS

Apps I build and run

Opens in a new tab

PRINCIPLES

How I work

The reasons behind the four promises on the home page

  1. I don't promise what I can't keep

    "Bug-free", "always on schedule", "guaranteed approval", "number one on Google" — those claims break eventually. Instead, I tell you up front what I can't do. I don't promise rankings; I handle registration and setup. I don't promise store approval; I fix the reasons for rejection and resubmit.

  2. Prices are set in writing, not on a call

    I don't quote a figure on the spot during a call. I write up what I heard as screens, features and timeline and send it to you, and that document becomes the quote. Quoting by time rather than a fixed total works the same way: if the scope grows, the document shows where.

  3. Bugs and changes are different things

    If an agreed feature doesn't work, that's a bug, and bugs get fixed however many rounds it takes — they're part of finishing the job. Small edits like swapping text or photos or adjusting colors and layout stay free after launch. For bigger changes, I tell you the added cost and time before touching anything, and never bill after the fact.

  4. I flag the monthly costs first

    Development is paid once, but server bills come every month and grow with your users. If your project needs a server — for accounts, payments or video — we agree roughly what it will cost and who pays before we start, so no one is left holding an unexpected bill.

  5. I hit problems in my own products first

    I still run four apps of my own. Store rejections, payment integration, multiple languages, deploys without downtime — I ran into them in my products before any client's, and I bring those fixes to your project.

CONTACT

LET'S
TALK.

Have a website or app in mind, a partnership idea, or a question? No logo or copy needed yet — tell us what you do and what you need, and we'll reply with scope, timing and a quote.