Hey Jonathon I’m playing catch-up – is there anywhere I read about the decision to migrate away from Avalonia? Just curious!
Sorry @lukxfnz, the short answer I should have given you 5 days ago is that we don’t have it written anywhere about the reasoning.
As is typical with changes of this sort, there are many reasons. Off the top of my head (I’m not making the big calls around here)
- Avalonia as a framework had very few people on the team thoroughly familiar with it.
- Moving to a web-based framework allows us to bring visual alignment between the web and desktop
- Some UI glitches in dui2/Avalonia couldn’t be fixed (thinking about tab navigation, returns not returning properly…
- If a new UI component was needed, it needed to be fully MVVC modelled from a limited set of Avalonia base components - the web is more flexible/immediate/hackable…
- … well I said it off the top of my head
In short, I think it was a better fit for the team’s broader skills to move to a native web UI framework and the visual identity across platforms.
2 Likes