@RickClephas

Attempting to create the apps of the future | Lead Developer @Ketjapp | Kotlin Multiplatform | Security and privacy enthusiast

 Nederland
github.com/rickclephas
Joined January 2016
  • Tweets516
  • Following118
  • Followers761
KMP-ObservableViewModel now supports the Observation framework 🚀 github.com/rickclephas/KMP-O…
1
6
359
Configuring proper crash reports for your Apple Kotlin Multiplatform application is only a single line of Swift code away with the revamped NSExceptionKt API. github.com/rickclephas/NSExc…
Code snippet showing the required configuration for Crashlytics and Bugsnag

ALT Code snippet showing the required configuration for Crashlytics and Bugsnag

1
7
63
4,663
Just noticed this Kotlin icon next to my KMP stack trace. Nice little detail by @getsentry! 💜
Screenshot of the Sentry dashboard showing an iOS Kotlin Multiplatform crash with nice little Kotlin icon.

ALT Screenshot of the Sentry dashboard showing an iOS Kotlin Multiplatform crash with nice little Kotlin icon.

1
13
1,517
Using KMP-NativeCoroutines just got a lot easier with the IntelliJ/Android Studio plugin
2
7
1
80
6,804
In 2023 checks and quickfixes are coming to KMP-NativeCoroutines (hopefully soon 😇). Happy new year KMM friends! 🎆
Screenshot of IntelliJ showing the error message "StateFlow property is exposed to ObjC" with a quickfix to "Add '@NativeCoroutines' annotation".

ALT Screenshot of IntelliJ showing the error message "StateFlow property is exposed to ObjC" with a quickfix to "Add '@NativeCoroutines' annotation".

2
53
6,130
The ObjC refinement annotations are experimental, so don't forget to OptIn!
`build.gradle.kts` sample showing an `optIn` to `kotlin.experimental.ExperimentalObjCRefinement`.

ALT `build.gradle.kts` sample showing an `optIn` to `kotlin.experimental.ExperimentalObjCRefinement`.

1
1
Generating code? Give your annotations superpowers with the HidesFromObjC and RefinesInSwift meta-annotations:
A `GenerateObjCFriendlyDeclaration` annotation annotated with `@HidesFromObjC` and a `GenerateSwiftRefinement` annotation annotated with `@RefinesInSwift`.

ALT A `GenerateObjCFriendlyDeclaration` annotation annotated with `@HidesFromObjC` and a `GenerateSwiftRefinement` annotation annotated with `@RefinesInSwift`.

2
1
Use case #2: refine your API in Swift. The NS_REFINED_FOR_SWIFT macro for Kotlin:
A `Person` interface with a `name` property with type `Pair<String, String>`, annotated with `@ShouldRefineInSwift`. A Swift extension on `Person` with a calculated `name` property with a tuple type. The Kotlin `name` property is called `__name` in Swift.

ALT A `Person` interface with a `name` property with type `Pair<String, String>`, annotated with `@ShouldRefineInSwift`. A Swift extension on `Person` with a calculated `name` property with a tuple type. The Kotlin `name` property is called `__name` in Swift.

1
2
Use case #1: hide declarations from ObjC and Swift. Completely hide a part of your API from ObjC, or provide ObjC friendly Kotlin declarations:
A `myKotlinOnlyFunction` suspend function annotated with `@HiddenFromObjC`.

ALT A `myKotlinOnlyFunction` suspend function annotated with `@HiddenFromObjC`.

1
1
Kotlin 1.8.0 contribution #2: the HiddenFromObjC and ShouldRefineInSwift annotation. Improve your ObjC or Swift API! 🧵
Experimental Kotlin Native annotations `HiddenFromObjC` and `ShouldRefineInSwift`.

ALT Experimental Kotlin Native annotations `HiddenFromObjC` and `ShouldRefineInSwift`.

1
6
37
ObjCName is experimental, so don't forget to OptIn!
`build.gradle.kts` sample showing an `optIn` to `kotlin.experimental.ExperimentalObjCName`.

ALT `build.gradle.kts` sample showing an `optIn` to `kotlin.experimental.ExperimentalObjCName`.

1
4
Use case #4: define the exact ObjC class name. Don't like the top level ObjC class name prefix? Just specify your own very unique class name instead:
A `MyNotSoUniqueClassName` class annotated with `@ObjCName("MyVeryUniqueClassName", exact = true)`.

ALT A `MyNotSoUniqueClassName` class annotated with `@ObjCName("MyVeryUniqueClassName", exact = true)`.

1
3
Use case #3: ObjC/Swift friendly API. E.g. an Array that uses the ObjC/Swift naming conventions:
An `Array` interfaces. The `size` property is annotated with `@ObjCname("count")`. The `indexOf` function is annotated with `@ObjCName(swiftName = "index")` and it's `element` parameter is annotated with `@ObjCName("object", "of")`.

ALT An `Array` interfaces. The `size` property is annotated with `@ObjCname("count")`. The `indexOf` function is annotated with `@ObjCName(swiftName = "index")` and it's `element` parameter is annotated with `@ObjCName("object", "of")`.

1
4
Use case #2: omit argument labels. Some functions just don't need that explicit argument label:
A `setUserId` function in an `Analytics` interface. The `id` parameter is annotated with `@ObjCName(swiftName = "_")`.

ALT A `setUserId` function in an `Analytics` interface. The `id` parameter is annotated with `@ObjCName(swiftName = "_")`.

1
1
8
Use case #1: class name conflicts. E.g. add a "DB" prefix to your database classes:
A `Person` data class inside a `database` package annotated with `@ObjCName("DBPerson")`.

ALT A `Person` data class inside a `database` package annotated with `@ObjCName("DBPerson")`.

1
8
Kotlin 1.8.0 contribution #1: the ObjCName annotation. No more weird names in your ObjC or Swift code! 🧵
An experimental Kotlin Native `ObjCName` annotation with properties `name`, `swiftName` and `exact`.

ALT An experimental Kotlin Native `ObjCName` annotation with properties `name`, `swiftName` and `exact`.

9
32
5
208
Have been working on something... Soon KMP-NativeCoroutines will reuse original property and function names.
Github PR file diff showing the renaming of `timeNative` to `time` in the KMP-NativeCoroutines sample.

ALT Github PR file diff showing the renaming of `timeNative` to `time` in the KMP-NativeCoroutines sample.

1
2
37
Who wants nice Kotlin crash reports on iOS? 🙋🏻‍♂️ I have got something working for Firebase Crashlytics, Bugsnag and Sentry. README etc will follow soon. github.com/rickclephas/NSExc…
3
10
1
42
Replying to @RickClephas @ChristianSelig
Did a quick test and it might work 🙃. It's just that `UITraitCollection.current.userInterfaceStyle` doesn't return the system style inside the UIColor provider. But if you could somehow keep a copy of it (and keep it up-to-date) than something like the following will work:
1
Load more