using AACs Viewmodel, Is it ok to pass an Application Context within the viewmodel. I need to access a color from resources.

You might want to look at this blog post: https://medium.com/androiddevelopers/locale-changes-and-the-androidviewmodel-antipattern-84eb677660d9

Exposing IDs is a safer approach. That said it still smells to me.

By the way, if you need formatted strings and would like to expose something like

data class StringResource(val resId: Int, vararg formatArgs: Any?)

Is there any easy way to get the formatting strings lint check that is applied to

Context.getString

work on

StringResource

constructor calls?

@arekolek You need to use

@StringRes

annotation for that

I should have been more specific, I meant the

StringFormatMatches

check

Personally I prefer to expose non Android version of the state (a.k.a. Business Logic state) from my ViewModel and then my Fragment would observe and transform it with Android concerns (ex: string resources).

Yea but try to reframe from bringing framework specific stuff to your viewmodel. It will be stressful during tests

Refrain*☝️