A Frontend Developer’s View of a Full-stack Kotlin Application
summary
A working full‑stack Kotlin prototype: a Ktor server with an in‑memory database, a Kotlin/JS React web client using JS wrappers, and shared business models and RPCs compiled from one Multiplatform codebase. It uses Kotlin Multiplatform (expect/actual) for platform glue, kotlinx.serialization for JSON, Ktor and React (wrappers) with Gradle build config, shows IDE navigation from frontend call to backend implementation, includes JUnit and enzyme-based tests, and the posts/users/comments demo is available on GitHub and runs end‑to‑end.
AI-written summary · about
chapters (20)
- 0:00Full-stack Kotlin intro
- 2:12Kotlin Multiplatform for frontend
- 6:51Shared codebase benefits
- 8:38Platform APIs and limits
- 10:00Demo app architecture
- 12:13Kotlin Multiplatform Gradle setup
- 13:17Static vs interactive apps
- 14:19HTML with Kotlin DSL
- 16:08React with KMP integration
- 17:15Wrapping JS libraries
- 18:43Kotlin data modeling
- 19:46Entry point and state
- 21:13Platform services handling
- 22:39Expect/actual in KMP
- 23:46RPC between client/server
- 25:54Debugging KMP code
- 26:15Database and shared logic
- 26:57KMP testing strategies
- 28:01Frontend meets backend
- 29:44Q&A
related talks
47mBuilding a full-stack application in Kotlin
45mKotlin Fullstack
40mFull-Stack Kotlin
31mKotlin beyond Android
45mSpring and React on Kotlin: Phantom Pains of Full Stack
40mCreating Full-stack Web Apps with Kotlin DSLs
48mEffective Multiplatform Kotlin Development
33mUsing Kotlin for JS Client and JVM Server
