What if your Android app reloaded code like a web dev’s fever dream, but screamed along at native speeds?
That’s the hook behind SMS, a Simple Multiplatform Script language one dev cooked up after hitting Claude’s usage wall mid-push. Bullseye timing, sure—but the real story? Market dynamics in mobile dev are brutal. Kotlin’s king, Flutter’s flexing cross-platform, React Native’s hanging on. Yet here comes SMS, compiling to LLVM IR for zero-VM native runs on Android and desktop. No garbage collection, no malloc/free drudgery. Types? Inferred on the fly, var number = 42 and boom, it’s int.
Feels scripted. Runs compiled.
Here’s the killer bit.
“When code is loaded dynamically via HTTP is executed inside a sandbox and interpreted at runtime. This makes it possible to extend or modify application behavior without rebuilding the app.”
Hot reload isn’t just dev candy—it’s production-safe, sandboxed dynamism. Push code over the wire, app updates live. No full recompiles. Android devs, drowning in 30-second build times, take note: this slashes iteration cycles to seconds.
Why Build SMS When Kotlin’s Already Everywhere?
Kotlin’s got coroutines, null safety, Google’s blessing. But it’s verbose for quick scripts, rebuilds drag. SMS strips to essentials—script feel, LLVM backend. Desktop too, via multiplatform dreams. The dev pairs it with SML (QML-inspired UI, sans expressions) and Forge4D (Godot 4.6 base). Markdown for content, GLB 3D scenes out the box. It’s an ecosystem play, not a lone wolf.
And performance? Compiled mode maxes speed. Interpreter for dynamos. Dual-mode workflow: experiment fast, ship optimized.
But look—solo projects like this echo Lua’s 90s embed in games. Quick scripts atop C++ engines. SMS? Same vibe, but multiplatform, Godot-fueled. My unique take: this isn’t hype; it’s a stealth Qt revival. Remember Qt’s glory days? Cross-platform native UIs, scripting hooks. SMS could niche-carve accessible dev tools, pulling indies from Electron bloat. Bold prediction: if open-sourced wide, it’ll snag Godot mobile devs tired of GDScript limits.
Errors don’t crash silent either. Amiga-style feedback—useful, recoverable. App pauses bad scripts, you fix, resume. Feels alive.
Can Hot Reload Scale Beyond Dev Toys?
Production risks loom. Sandboxed HTTP loads sound slick, but security? Android’s no web server—permissions, tampering. Yet LLVM sandboxing + interpreter isolation mitigates. Market angle: enterprises crave this for A/B tests, remote fixes sans Play Store. Flutter hot restarts? Close, but restarts kill state. SMS? Stateful swaps.
Data point: Godot 4.6’s Vulkan renderer crushes Android perf already. Layer SMS logic? Hybrid apps blending UI, Markdown docs, 3D—all native. Docs as apps? Books? Niche gold.
Skepticism check. It’s early—one dev’s experiment. No benchmarks vs. Kotlin Native. Ecosystem? Forge4D’s unproven. But timing’s ripe. Post-AGI hype, devs crave simple tools. SMS bets on accessibility sans perf tax. Smart, if it ships.
Workflow wins big. Script fast. Native ship. Dynamic update.
Desktop + Android: Multiplatform Mirage or Reality?
SMS eyes desktop too—LLVM’s portable magic. Godot handles rendering cross-platform. Imagine: tweak 3D Android game logic live, push to web preview, desktop build. Unified dev? JetBrains dreams, but SMS feels lighter.
Corporate spin? None here—raw dev diary. No VC fluff. That’s refreshing in a sea of LLM-generated roadmaps.
Numbers game: Android’s 3B+ devices scream for efficient scripting. iOS? Apple’s walled garden blocks dynamos, but Android’s open.
Push a release, hit limits—Claude’s €20 sub fueled it. Universe winks.
This direction? Intriguing. Makes sense for tooling starved of fun.
🧬 Related Insights
- Read more: Filasys Promises Enterprise Analytics in One HTML Line. Really?
- Read more: VLIW: The Processor That Promised Too Much
Frequently Asked Questions
What is SMS scripting language?
SMS is a simple scripting language that compiles to native code via LLVM for Android and desktop, offering script-like ease with no VM or GC overhead.
How does hot reload work in SMS for Android?
Dynamic code loads over HTTP into a sandboxed interpreter—no rebuilds or reinstalls; changes apply instantly to running apps, safe for dev and production.
Can SMS replace Kotlin for Android apps?
Not fully—Kotlin’s mature ecosystem wins for scale—but SMS shines for rapid prototyping, dynamic updates, and multiplatform with Godot integration.
