Hi, I’d like to share a project that I was workin...

# feed

[GarouDan]

Hi,

I’d like to share a project that I was working on:

Universal Kotlin is a project that aims to run on the most popular platforms using just Kotlin.
Also, one of its goals is to use shared code from the common modules and libraries in all other ones.

The current supported implementations are

- buildSrc
- common (multiplatform)
	- multiple source folders
	- single_source folder
- library (multiplatform)
	- multiple source folders
	- single_source folder
- application
	- backend
		- jvm
			- spring boot
	- browser
		- js
			- spa
				- react
			- vanilla javascript (kotlin only)
		- native
			- wasm32 (kotlin only)
	- desktop
		- jvm
			- tornado fx
	- mobile
		- jvm
			- android
		- native
			- apple
				- ios
					- iosX64 application copying a kotlin framework
					- iosX64 kotlin framework (for reuse)
					- iosX64 application with a kotlin framework embedded
					- iosX64 application withtout a kotlin framework
	- script
  		- jvm
  			- kscript
	- terminal
		- jvm
			- terminal (jvm terminal application)

https://github.com/funttastic/universal_kotlin

[Joost Klitsie]

Now posting this comment on the proper post: It looks really cool (and a bit overwhelming at first 😄 ) I have a question for the android application: why do you apply there the multiplatform plugin instead of the application plugin? Is that necessary?

[GarouDan]

Hi @Joost Klitsie, initially I was trying to use the kotlin multiplatform plugin for all “applications” but after some time I’ve seen that this is not always possible. But at least one issue that I raised for Spring Boot for example was solved by JB because of that. That’s the “why” for the android app. But I’d like to simplify the architecture a bit more in the future and this is a good point. Basically my dream is to write for everything using just one language and it is really cool that Kotlin is providing something like that for us, but the puzzle is not easy to solve