Appbox

What it is

Appbox is a no-code app builder that turns a website you already run into an Android or iOS app. Its homepage headline reads "노코드 앱빌더로 30초 만에 앱으로 만들어보세요" (build an app with a no-code app builder in 30 seconds). It is aimed at founders, small businesses, early-stage startup teams and one-person companies that have a mobile website but no app team. The site is written in Korean, and the company behind it is Mobile Partners Inc. (주식회사 모바일파트너즈), with a business address in Mapo-gu, Seoul.

The approach is a WebView app: your live website runs inside a native shell, and the platform adds native capabilities and a messaging console on top. The company describes the shift as moving app development from "building from scratch" to "connecting" an app channel to a site you already have.

What you build and how

The build flow is short. In the console you sign up, create a new app and enter 3 things: your website URL (the company's example is a shop address), an app name and an app icon uploaded as a PNG. You choose Android or iOS, and the cloud build starts. The company says the build takes about 30 seconds, and it runs on its servers, so you don't install Xcode or Android Studio. When the build finishes you get a QR code, scan it, and the app installs on your phone. The homepage also offers a demo: type any website address and you get a sample app screen to try, again through a QR code.

Because the app loads your site, changes you make on the website show up in the app. The company's blog says "웹을 수정하면 앱이 자동으로 업데이트됩니다" (when you edit the web, the app updates automatically), with no store review wait for those changes. Its example is an event banner posted in the evening that app users see the next morning. The same blog says the QR route lets you deploy "without app store review", which it pitches for internal company distribution and for demos before an investor or client meeting.

The part that separates it from a plain site wrapper is the native layer. Appbox says the console offers "50개 이상" (more than 50) native features for the web app. Its blog names biometric authentication, QR scanning, location services and PG payment (the Korean payment gateway model) among them. These are reached through what the company calls JavaScript Bridge technology: your web code calls the native function directly, so a login page can trigger biometric auth without a separate native screen.

Messaging is the second half of the product. Push messages can go to all installed users or to a segment. In-app messages show popups and banners while the app is open, built from supplied popup templates. After a push goes out, the console reports the conversion rate, meaning how many recipients opened the app, and the homepage mentions tracking results through to sign-ups, events and purchases. The company's homepage claims in-app messages produce "푸시 대비 200% 이상" (more than 200% of the engagement of push) and that reaction data is analyzed in under 1 second. Those are the company's own claims. The homepage groups the value it promises under 3 headings: cost savings, because a no-code build means "별도의 앱 개발팀이 필요하지 않습니다" (no separate app development team is needed), higher conversion through tailored messages, and return visits driven by precise targeting.

For developers, the navigation carries a developer center with an SDK guide, an app integration guide and a console user guide, and there is a downloadable solution brochure. The homepage also says the service covers "신규 앱 제작부터 기존 앱 업데이트까지" (from new app creation to updating an existing app).

The mobile-apps membership is a fair fit with this: the output is a real installable Android or iOS app, not a bookmark. What you design is limited to the basics the site shows, the name, icon and URL, plus whatever your website itself looks like.

Plans, pricing, and evidence

The homepage links a pricing page (요금제) but prints no plan names or monthly figures itself. What it does say is how the free side works. The homepage states "무료로 사용하고 성장하면 비용을 검토하세요" (use it free, and review the cost as you grow) and "앱박스는 매월 무료로 일정 발송 건수를 보장합니다" (Appbox guarantees a set number of free sends each month). A line near the bottom says the web app features are free permanently: "웹앱 기능은 영구 무료로 사용하고, 비즈니스 성장에 맞는 플랜을 선택하세요" (use the web app features free forever and choose a plan that fits your growth). The navigation has a pricing page, and the main call to action is a free app build trial.

Store costs are separate from Appbox. The company's blog notes that the Apple Developer Program is $99 a year and a Google Play account is a one-time $25, and says these apply whichever builder you use. The QR route is how it suggests skipping them for internal rollouts and demos.

The blog also argues that most of an app's hidden cost comes after launch. It says OS updates break native apps and force rebuilds, while a WebView app picks up web changes at once, so most maintenance falls away. It also says that sending even a single push from a conventionally built app means wiring up a messaging service and subscribing to separate marketing tools, whereas in Appbox the push and in-app message features connect to the console as soon as the build finishes. It cites a minimum of 10 million won and 2 months for an app 2 years ago as the old answer to what an app costs.

Company figures on the homepage: more than 100 million cumulative messages sent ("1억+"), and "100%" domestic development and operation, meaning built and run in-house in Korea. Support runs through a solution inquiry form, the developer center guides and a downloadable solution brochure, and a separate terms of service covers the message sending service.

Who it suits

Appbox suits a business with a working responsive website and no developers: a small online shop, a franchise, a small or mid-sized company, a public body, or a solo founder who needs a real app on a phone before a meeting. It is also a reasonable fit when the point of the app is re-engagement, since push, in-app messages and conversion stats arrive with the first build rather than as a separate tool. The site and its guides are written in Korean, so a Korean-speaking team will find the documentation easiest to use.

Be clear about the limits. The company itself lists the cases where it recommends writing the app directly: when the app is the product and needs full customization, when it needs hardware integration that the web can't reach, and for games or AR and VR needing high-performance rendering. The app is also only as good as the mobile site inside it, so a slow or awkward site stays that way. The blog's own piece on social login in a WebView shows that sign-in with providers other than Google needs redirect, cookie and popup handling, so test your login flow early.