The stuff I've been directly building in the last few years has just been PWA/WebView, because web stack is reliable and even more "single development platform", but I've been keeping something of an eye on MAUI in case it grows up into something great. NET NativeAOT versus classic Mono AOT are fascinating.) (Also the in-progress performance metrics of the. NET 8 MAUI development and that piqued my interest again in MAUI. I was looking at the newly announced VS Code extension for. Again the Tamagui starter repo `npm create tamagui` has this set up and its a whole ton of work saved in terms of getting that right. The biggest part is getting a monorepo set up properly with shared code. For simple apps you can get away with just something like React Query and Reacts useState, for more complex one of Daishi's state management libraries (everyone has their different preference, I love the black sheep Valtio), or the new kid on the block Legend State looks interesting. It uses Supabase for data and auth, which seems to give the best overall package for data and auth.įor state depends entirely on the complexity of app. I made Tamagui (with much effort) to solve this, which has probably the best setup out there at the moment for sharing your UI code on the frontend: įor backend we're working on a starter kit that puts together all the pieces (there are a lot!) that's days from release, if you reach out on the Discord I can help get you on as a beta tester. It's more of a problem if you have a shortage of money, at which point, you should just use whatever you can build with the quickest to keep your business afloat. But I honestly never experienced a shortage of people. The main problem could be talent, as if you have specialised people, you always have to hire for both of these positions (or train your people in either direction internally). You could say that the same people do that with the same stack, but in my experience, if you allow people to put more focus on the one component they're building, they'll just build it better than when they have a plethora of other dependencies to consider. Instead, now that we have backend (Go) & frontend (TS) teams at my work, both teams consider the best practices for each environment with more focus. The reason I'm saying this is because that often leads to some very messy dependencies, and maintaining that codebase can become really difficult if you're not very careful.Īdditionally, I found that in some teams, people would use some backend code on the frontend, resulting in some security vulnerabilities (server-side logic running on FE instead of BE). On the opposite, I find that sharing code across full stack is becoming overrated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |