Hi Warren,


This is a very clean and practical approach to handling version control in Power Apps, especially using a central parameter list and conditional visibility. I like how lightweight and easy to maintain it is.

One thing I’ve seen in similar implementations is that version comparison can become tricky depending on how version values are stored and compared.

For example, when versions are treated as numbers:

2.1 and 2.10

Both evaluate to the same numeric value (2.1), even though semantically they may represent different release versions. That can make version enforcement harder as applications evolve.

To make comparisons more predictable, I’ve had success treating version components explicitly instead of comparing the full version as a single number.

For example:

Major = 2
Minor = 15

Then compare Major and Minor separately.

Alternatively, if keeping a single version field, enforcing a consistent format (for example 2.01, 2.15, 2.90) can also work well and keeps the implementation lightweight.

Overall, really nice pattern, simple, effective, and easy to extend.