Kotlin API Design Review

Naming Rules

• Clear at point of use
• Omit needless words
• lowerCamelCase: properties, functions, variables
• UpperCamelCase: classes, interfaces, objects
• UPPER_SNAKE_CASE: constants
• Booleans: is, has, can, should prefix
• Collections: plural names (users, not userList)

Compose-specific Naming

• Composable functions returning Unit: use PascalCase nouns (e.g., UserProfileCard, not userProfile)
• Avoid spaces and backticked identifiers in function names, especially in public APIs (discouraged by Kotlin conventions)

Common Issues

| Issue | Fix |