IMHO, now is a great time to use native Swift/Kotlin code alongside shared Rust code via UniFFI

massel 5 hours ago | parent | next [-]

We've been doing this for a while and it works great. Logic and network stuff goes in Rust, UI goes in Swift/Kotlin.

rvz 6 hours ago | parent | prev [-]

So you want to review and maintain code in 3 separate languages?

Sounds like a complete waste of tokens with the worst case of just quickly building more technical debt, three times.

It's a lot nicer than having the same logic in 2 languages and trying to keep them in sync – whether doing it by hand or with an LLM.

One of the big rules is don't repeat yourself – much of the logic only needs to be written once (except UI)

	▲	mike_hearn 5 hours ago \| parent \| next [-]
		Rust is uncompetitive for the use case of sharing logic between mobile apps. Kotlin has Swift interop and KMP is a mature tech by this point.
	▲	doc_ick 5 hours ago \| parent \| prev \| next [-]
		Well you don’t repeat yourself if the llm repeats it for you at the cost of millions of tokens.
	▲	rvz 5 hours ago \| parent \| prev [-]
		In that case, Kotlin makes even more sense especially with Kotlin Native, and Rust is unnecessary. Kotlin is already multi-platform and can be re-used as the business logic in iOS apps with Swift as the UI and the Android app with a Kotlin UI (Jetpack Compose) or both iOS and Android apps can be written entirely in Kotlin. That vastly reduces the maintenance and Kotlin is reused across all apps and keeps it at 2 languages at most. No need to introduce Rust to achieve the same goal.