x:DefaultBindMode="OneWay" has no effect for iOS/Android while it works perfectly for UWP [and WASM (as a bug at the moment)].

x:DefaultBindMode="OneWay" should work

Repro:
https://github.com/zipswich/AppDebugUno
Nuget Package:
Uno.UI
Package Version(s):
2.1.0-dev.1338
Affected platform(s):
Visual Studio:
Relevant plugins:
In fact this is not yet implemented on any platform, in case of WASM it seems to be a bug instead, that x:Binds now behave as TwoWay, even when they are not
in case of WASM it seems to be a bug instead, that x:Binds now behave as
TwoWay
That is a surprise. I need to keep this in mind. Microsoft's choice of 'OneTime" as the default is irrational unless the initialization of "OneWay" binding is significantly more expensive.
I updated the content of this issue to reflect the latest info, thanks so much @MartinZikmund & @zipswich :) !
Other related PR for x:Bind (https://github.com/unoplatform/uno/pull/2702)
@zipswich OneWay is more expensive than OneTime for sure, even in Uno. OneWay and TwoWay need to hook to INotifyPropertyChanged and DependencyProperty changes.
Is the hooking process quite expensive or the actual calling of handlers of INotifyPropertyChanged expensive. My original understanding was the latter. The handlers are never called (at least for my apps) for those bindings that need only one-time binding because their values are not changed. If it is the former, then I can understand the rationale.
@zipswich hooking can be expensive, as it needs to be done on all levels. It's not particularly expensive per binding, but if there are many, it can add up :)
Most helpful comment
@zipswich OneWay is more expensive than OneTime for sure, even in Uno. OneWay and TwoWay need to hook to
INotifyPropertyChangedandDependencyPropertychanges.