Modeling

How should we be thinking about modeling the views, especially those that differ by platform and as the repo grows over time?

Could imagine the #if method getting messy.

As I was building this in the first place, I imagined making a struct to hold each grouping and an array of views inside of it. Curious if there are other suggestions and if doing this might be overkill?

The issue names no files or tests. Start by locating the platform-specific #if branches and the existing view groupings referenced in the discussion, then compare how views differ across platforms. Done would require agreement on a scalable modeling approach before implementation; the issue does not define that approach or a concrete acceptance test.

Written by the indexing model from the issue text.