It is guessable with nanosecond + ( endians.length * endians.length ) combinations. (By the way: if you combine (xor) two random values, the result is always at least as random as the most random of the both).Īctually I want timestamp based shorter unique identifier, hence tried the below program. (If you create a the UUIDs only once per second, then it is a good idea to add a time stamp) So the way is simple: create a 6 byte random array SecureRandom rand Īnd then transform it to a Base64 String, for example by .binary.Base64īTW: it depends on your application if there is a better way to create 'uuid' then by random. This means 6bit per char, so you get 48bit in total (possible not very unique - but maybe it is ok for you application) If you want a unique string with length 8 printable characters you could use a base64 encoding. Second: I assume that when you talk about 'only 8 characters' you mean a String of 8 normal printable characters. So it is at least a risk based decisions, how long your uuid must be.

So if you reduce it to 64 bit, 32 bit, 16 bit (or even 1 bit) then it becomes simply less unique. actual fun randomUUID () UUID.randomUUID (). Especialy UUID.randomUUID is 'only' a 128 bit (secure) random value. As per the Kotlin multiplatform documentation, you can make an expect/actual function to use the Android (java) and iOS (NSUUID) specific implementations: // Common expect fun randomUUID (): String // Android import java.util. First: Even the unique IDs generated by java UUID.randomUUID or.

Kotlin uuid