Why There's Almost No 'Liferay + Kotlin' Content Yet — and the KDXP Demo Changing That
This is LR Tools’ write-up of a follow-up post by Nestor Ledon on Liferay.dev, revisiting the KDXP project a few weeks after its initial announcement with a concrete setup demo.
A capable backend without a modern client story
Liferay already gives you a mature backend for content, permissions, users, sites, workflows, and headless APIs — that part isn’t in question. What’s been genuinely missing is a practical, modern way to use that backend to power a cross-platform client application. Liferay used to ship dedicated mobile SDKs, and retiring them in favor of Headless Delivery was probably the right architectural call — a REST/GraphQL-first backend is more flexible than a bespoke SDK long-term — but it left a real developer-experience gap in the meantime, since nothing else stepped in as a direct replacement. API-first platforms like Contentful have already made the case that separating a backend from its presentation layer pays off; Liferay has the backend half of that story, just not yet an equivalent client layer.
KDXP — introduced as a Kotlin Multiplatform framework built directly on Liferay’s headless APIs, targeting Android, iOS, desktop, and web from one codebase — is positioned to fill exactly that role, not as another platform-specific mobile SDK.
How thin the gap actually is right now
One data point makes the gap concrete: searching YouTube for “Liferay Kotlin,” and separately for “Liferay multi-platform,” currently surfaces the KDXP setup demo on the first page of results for both. That’s not evidence KDXP itself is mature — it’s evidence of just how little content exists right now at the intersection of Liferay and modern cross-platform tooling. (Those search results were captured August 4, 2026, so take them as a snapshot rather than a permanent state.)
What the demo actually covers
The setup demo walks through connecting KDXP to a local Liferay installation, configuring OAuth, and creating an application-backed site — the concrete first steps of getting a KDXP client talking to a real Liferay backend, rather than a purely conceptual pitch.
Where this is heading
The framing here is deliberately modest: this is presented as a first step toward giving Liferay developers a shared application layer across Android, iOS, desktop, and web — not a finished cross-platform story yet, but a starting point for one.
This article is LR Tools’ write-up of the original post by Nestor Ledon — read it on Liferay.dev for the author’s own framing, or watch the KDXP Liferay setup demo directly.
Dieser Artikel ist adaptiert von: Nestor Ledon, Liferay.dev