Need help with kotlin-full-stack-application-demo?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

199 Stars 40 Forks 102 Commits 2 Opened issues


Full-stack demo application written with Kotlin MPP

Services available


Need anything else?

Contributors list


Fork of with the new Kotlin/JS Gradle Plugin

A full-stack demo application written in Kotlin for JetBrains Night Moscow 2019.


Run application

  • ./gradlew :server:run
    will build optimized application bundle and run it on https://localhost:8080 (it takes some time to build optimized js bundle, so it is not useful for frontend development)
  • ./gradlew :client:run -t
    will run development application at https://localhost:8080 with live reload. It runs ktor and webpack dev servers under the hood:
    • Webpack dev server will be started at the front https://localhost:8080.
    • Ktor server will be spawend internally at https://localhost:8081 in separate gradle process (webpack devserver will start it)
    • Webpack dev server will call ktor for everything expect


  • ./gradlew :server:build
    will create
    . You can deploy it on the server and run
    to start the server. Client is included into the


This application displays a feed containing user-generated posts and comments. All data is stubbed by the fakeJSON and JSON Placeholder services.

It is a Kotlin Multiplatform project.

It uses: -

plugins for Kotlin compilation; - Ktor framework as a web server; - H2 in-memory database with Exposed to preload posts at application startup; - kotlinx.serialization for client/server (de-)serialization and RPC; - React, Styled components, Ring UI 2.0 and kotlin-wrappers for rendering.

During application startup posts are preloaded to the in-memory database from the fakeJSON (or JSON Placeholder) service. When the user requests the page, several posts are selected from the DB and the corresponding comments are fetched via the multi-platform HTTP client. Posts with comments are served to the client via RPC. After the initial render is done, information about authors is fetched via the client-side HTTP client and rendered after all coroutines terminate successfully. The "Load more comments" button fetches additional comments for the post using the multi-platform HTTP client.

This application has no error handling and has very limited RPC serialization. It's not meant for production use and serves only as a technology example.

Contact information

Please refer original repo:

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.