"Add schema" opened the editor on the two fields every list has and left the member to build the rest. curare.to's /new page does it the other way round: a "Start a list" picker of four shapes -- links & text, discussion, catalogue, custom -- and an editor seeded from the one chosen. The button now pushes SelectCuratedSchemaTemplateScreen, that picker on a phone, and a card pushes the editor with the template's key, the same word the site takes as ?template=. Back from the editor is the picker and another shape; when a new list's proposal goes out the signing session replaces both. CuratedSchemaTemplate is lib/protocol/templates.ts field for field, with CuratedDeriveRule for the [rule:<key>] mark the site records in the identifier field's hint -- its own convention, not the NIP's, and the thing that lets that site's form derive an entry's d for a list the group starts here. The hint is written byte for byte as the site writes it; the app still composes no suggestions and applies no rule. Null or an unknown key seeds Custom, which is the bare two fields the editor opened on before, so a screen handed no template behaves as it did. The picker's one departure from the site: its cards list a template's fields by label, the way the group's schema cards do, rather than counting them -- what an entry asks for is what the choice is made on. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform…