I would use whatever back-end you’re most comfortable with. For me that’s probably C#, but any solid language will do. I also recommend considering something l

I would use whatever back-end you’re most comfortable with. For me that’s probably C#, but any solid language will do. I also recommend considering something like GraphQL for your API interface as it will reduce the amount of times you have to dip back into the back-end to add a single property to a response or write a new optimized endpoint for a particular view. Front-end IMO it really depends on what you’re trying to build, React Native doesn’t really reduce your overall work IMO so much as the cognitive load. You still end up not only having a separate codebase from your web UI but also have to at times dip into xcode and angular studio to write some platform-specific code. I would probably explore Flutter if I really needed to write something once, but I can’t really comment on it today. For the stuff I work on I usually just try and make the web experience as mobile-friendly as it can be and leave it at that. For B2B customers that’s almost always sufficient anyway. I tend to work in Angular more often than React and have been pretty happy with the amount of reuse I get between projects and the quickness of the dev loop.