Are there any limitations to using One-Time binding in MvvmCross

1. No Continuous Updates: The primary limitation of One-Time binding is that it does not continuously update the View based on changes in the ViewModel. This makes it less suitable for dynamic data that needs to be reflected in real-time on the UI.

2. Static Data: One-Time binding is best used for static or read-only data that does not change frequently. For example, it is often used for setting static text from language files, as the language selection is typically made once and not changed frequently[1].

3. RecyclerView and Similar Controls: In controls like `MvxRecyclerView`, One-Time bindings may not behave as expected due to view recycling. When the user scrolls through a list, views are recycled and reused, which can cause One-Time bindings to re-fire, effectively behaving like continuous bindings[4]. This can lead to unexpected behavior if not managed properly.

4. Performance Considerations: While One-Time bindings do not monitor changes, they do not inherently introduce performance issues. However, if used extensively in complex layouts or with many bindings, the initial setup might contribute to slower UI rendering times compared to other binding modes[9].

5. Thread Safety: MvvmCross bindings, including One-Time bindings, can be affected by threading issues if not properly managed. For instance, if bindings are executed on a worker thread, it might lead to unexpected behavior unless properly synchronized with the UI thread[5][3].

In summary, while One-Time binding is useful for static data, it is not ideal for dynamic data or scenarios where continuous updates are necessary. Additionally, its behavior in certain UI components like `RecyclerView` requires careful handling to avoid unexpected rebindings.