I’d probably use razor pages rather than mvc. But your the server code needs to be layered. You might focus on the rest api used by mobile app first. The api code should be nothing more than mapping the api parameters to the business objects that do the work.
you could also do the same functionality in the web and the mobile at the same time. This will encourage sharing the code via refactoring.
on design issue will be ui state management. The mobile app has state, but the web site will not. You will want ui state management abstracted and not part of the shared server code base.
you will also want to consider authentication. The website will use cookie, but the mobile app will probably use bearer tokens.