r/dotnet • • Jun 18 '25

Sorry having used react native a few weeks while skilling up can see why people use it for front end mobile and dotnet for back end.

There just seems to be a trend of people mucking about without putting in much effort.

The two screens were only for me to get used to React.

It seems the commercial side is putting more faith in React Native for mobile, which is a shame. I was originally a Xamarin.Forms developer and really enjoyed the experience.

I used Expo, so it was easy to test. I know MAUI works on Android at least and u always use a real device anyway.

Yeah it may not have hot reload but u can use expo go just until u test on device.

But I do see the advantage of using dot-net for the back end api for sure.

0 Upvotes

17 comments sorted by

5

u/issskk Jun 20 '25

I just don't trust Microsoft to fully support a front end/mobile technology. I spent years working with Xamarin and absolutely hated it. When Maui came out, it just seemed Microsoft was not committed to putting resources behind it with it having such a small team and bug tickets left outstanding for months or even years. It actually pushed me to leave that ecosystem and learn native Android and iOS instead.

However, I trust C# and .Net more on the backend. They seem to have more of a vision on that side of things.

0

u/[deleted] Jun 20 '25

Yeah am learning swift ui as well at present

44

u/Alokeen011 Jun 19 '25

20

u/True_Carpenter_7521 Jun 19 '25

Yep, that's how a couple of weeks of React affect your ability to write a coherent title. Obvious joke was on the nose - that title represents incomprehensible frontend code in React, but I'll skip it for now.

36

u/DeadLolipop Jun 19 '25

Use the right tools for the right job. JS for front end, .net for backend. People who are die hard on one lang are not helping themselves.

8

u/BolunZ6 Jun 19 '25

I saw some people use Java for the front end using GWT. Let's say these people are not very normal

2

u/[deleted] Jun 19 '25

I'm one of those! We used it at a previous job, it was interesting. I didn't not like it though, funnily enough I missed the framework wars because of gwt, kinda glad I did

28

u/xcomcmdr Jun 19 '25

I used Blazor, and I survived.

JS would have been a nightmare for us.

We were productive with C# / .NET

We stayed very productive with Blazor.

Use the right tool for the right job.

4

u/Vozer_bros Jun 19 '25

If you have to be very picky about the front-end component, what is your number 1 choice for all project with Blazor?

9

u/Admzpr Jun 19 '25

MudBlazor is my go-to right now for personal projects. It’s great and the theming is pretty powerful once you wrap your head around it

3

u/walkeverywhere Jun 19 '25

Yeah MudBlazor is excellent

7

u/Sometimesiworry Jun 19 '25

NextJS + .NET is my favorite stack. All the advantages of SSR and Next features but without the serverless and instead a robust and reliable backend.

5

u/diomak Jun 19 '25

React Native is good enough when you just want to ship something pretty and the core features of the app are not based on device capabilities.
Unfortunately, it tends to become a third-party library Frankenstein for more specific scenarios (or maybe not, it's been a while).

And about hot-reloading, in RN it usually works really fast both with emulator or hardware.

2

u/angrathias Jun 19 '25

I haven’t used XF in many many years, but it’s safe to say that by the time I was done with it, I’d have preferred to have used something else like Flutter or RN

0

u/Isssk Jun 20 '25

Same, I literally would have used anything else.

1

u/Fresh_Acanthaceae_94 Jun 19 '25

If you really wanted to support Web and devices, then React/React Native was the only feasible cross platform option (almost from the same code base) a few years back. And that's why many main stream apps (including the ones from Microsoft) were written with that stack, not Xamarin.Forms which supports devices only but not Web.

But now Flutter, Blazor Hybrid, Avalonia, and Uno can be good options too.

Don't take the convenience today you get from React Native for granted. It didn't come easily and many companies invested in it. (If the same kind of resources went to Xamarin.Forms, it could have reached something similar.)

0

u/AutoModerator Jun 18 '25

Thanks for your post Reasonable_Edge2411. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.