You have 2 options.
- No Mvvm. You can use classic approach to write your code behind if you are familiar with Windows Forms for example. This faster and straightforward approach without any Mvvm boilerplate. Also easy to manage XF default navigation.
Disadvantage is probably the separation of your business logic and UI. So it will be harder to do Unit testing, mocking etc as you may have some references of Xamarin.Forms. - Using Mvvm. If you are familiar with Mvvm, I would you recommend you to use Mvvm binding. By that you can separate your UI logic with business logic. Later migration to Maui will be easier.
Here you have a few options.
- MvvmCross and Prism; quite advanced and complicated. they also increase your App size.
- Freshmvvm; easy and light weight. I can recommend this. But sometimes it may not fullfill your requirements.
- Mvvm Light; also light and easy to learn. I have used it for Wpf but dont know how is it today for XF.
Best is not to use any library but use standard mvvm. if you need to use one, use freshmvvm if Prism is too complicated for you