SwiftUI or React Native?

1.Uno: Create Beautiful Cross Platform .NET Apps Faster

Other than the already mentioned JavaFX which now goes by OpenFX due to Oracle’s TM license changes, there’s also- Swing with FlatLaf look and feel, just exactly like the JetBrains IDEs, there’s a kitchen sink app JAR you can download from FlatLaf, there’s some nice extensions for the layout too, not for mobile though as far as I’m aware- Vaadin and their 2nd framework whose name I forget, directly integrated with Spring and Quarkus- Kotlin Multiplatform and Jetpack Compose Multiplatform, a very promising and awesome tech, works fine for my requirements, would be happy for them taking the lead, I love the syntax and their compositional semantics, similar to SwiftUI- React Native worked great for me, can reuse some React.js stuff- NativeScript, never tried- Ionic Capacitor, never triedI think it might make sense to watch a couple YouTube live coding showcase sessions with the respective developers.Avalonia also has a kitchen sink app btw. And I really like Uno’s calculator app, though I recall having had a weird bug once in the calculation logic.And as for Blazor, there’s always been JSF which have long had great UI components. To me Blazor is about replicating JSF.Yeah, well, I wish there were just 1-2 really good choices to be made, but there’s a myriad of caveats in each framework, more so in some of them. Well, Qt comes closest I think.

2.Ask HN: Freelancer? Seeking freelancer? (November 2023)

SEEKING WORK | Austin, TX (UTC-5) | REMOTE and Austin LocalI have a lot of wide-ranging experience, but will provide the most value to your organization if you need some combination of Rust, AWS/DevOps, and Kubernetes expertise.<pre><code> Senior Software Developer - Infrastructure, 9+ years experience Backend: Rust, Elixir, Go Mobile: Swift/SwiftUI, React Native DevOps: Kubernetes, AWS, GCP, Pulumi, CDK, Terraform, ArgoCD Certs: AWS Solutions Architect (Associate) Email: [email protected] Availability: 20 - 40 hrs / week </code></pre> * 4+ years of experience with AWS, GCP and Kubernetes with both small startups and larger organizations* 3+ years of experience with Rust, 9+ total experience (Elixir and Phoenix)* Some frontend and mobile work with React and ReactNative (JS & TS)Things to checkout:GitHub: <a href="https://github.com/praveenperera">https://github.com/praveenperera</a>Blog: <a href="http://praveenperera.com/blog" rel="nofollow noreferrer">http://praveenperera.com/blog</a>YouTube: <a href="https://www.youtube.com/channel/UCm8urFQRWUEGpaDhdvmeYkQ">https://www.youtube.com/channel/UCm8urFQRWUEGpaDhdvmeYkQ</a>You can contact me at [email protected]

3.Ask HN: Who wants to be hired? (August 2023)

Location: Rochester, NY Remote: Yes Willing to relocate: No Technologies: Swift, SwiftUI, React Native, Objective C, Kotlin, Mobile Development Resume: <a href="https://www.linkedin.com/in/jonathan-kidney" rel="nofollow noreferrer">https://www.linkedin.com/in/jonathan-kidney</a> Email: [email protected]

4.Ask HN: Who wants to be hired? (August 2022)

<pre><code> Location: EU Remote: Yes Willing to relocate: Rather not, but if that's sunny place where you can surf I might consider it :) Technologies: Swift, SwiftUI, Objective-C, Ruby, Ruby on Rails, JavaScript, HTML, CSS, Java, Python, RxSwift, Combine Résumé/CV: Available upon request Email: [email protected] </code></pre> I'm a product-focused iOS engineer specializing in high-scale apps used by millions of users. 8 years of experience in mobile development. I'm open for any mobile related work, Web3 projects are welcomed. I'm open to work in Swift, SwiftUI, React Native. If there's need I can switch to a different technology. I would love to work at a company with a mission that resonates with me and with a product that brings real value to the users.

5.Dead ends of information technology

> no one is even attempting to improve the state of native GUI development as a resultSwiftUI, React Native, Flutter disagree with you

6.Ask HN: What rapid development framework do you use for your MVPs?

Long post, but I hope it helps someone out since it covers web,mobile, etc. MVP to me means being able to build something quick and iterate upon, so while it could be a throwaway project each time it still makes sense to have a preferred solution for each problem space.I stick to tech I know best and also languages which offers a vast variety of available SDKs and dependencies to consume so I don't need to waste time re-inventing the wheel. I also try to plan for my requirements up front so I can best prepare. In this case, I am building an application that requires authentication, notifications, private + group chat, location awareness, and an admin sites for the CMS, partner portal, etc.- For data storage, I use postgres for persistence, and redis for caching and other temp things. I'm not an expert at either of these, but I have used both extensively and have enough experience/interest to work through any issues that may come up.- I use nodeJS + express to write backend services. Example: My web and mobile clients consume a REST service that interacts internally with a data layer service. Since the code is organized very simply and modular, it makes it easy for me to spin up new services that consume existing services, or makes it easy to extend. I have a real time service that could use the same data layer service if needed.- I try to use SDKs that can solve my problem cheap + quick. This is where planning up front is also valuable because if you can identify which SDKs are available for the languages you are using, you will save lots of time and pain. For example, I'm using connectycube (free up to 10k users) for video + chat because they have flutter SDKs it takes literally 10 minutes to set up and be most of the way there. I use firebase for authentication (its free) on the clients, and for my REST service token verification. Firebase can also handle push notifications, so keep that in mind! I use mapbox for geocoding because it is cheaper than google maps.- For infrastructure, I was using AWS but switched to DO managed postgres and droplets. I'm still using S3 and cloudfront.The reason I did this is because I don't have much infrastructure experience and made a few misconfiguration mistakes on AWS that bit me. DO makes it dead simple for now so I can focus on just building my product and maybe some day I will be lucky enough to work with a team who knows AWS :)- For web, I have the website (hosted using carrd, dead simple website builder. They have a cheap paid plan that lets me do things like add a contact us widget and add a google analytics), while the CMS and partner sites are being built using create-react-app. There is no consumer web app (mobile app only), so really those users will just see the site and go download the apps. Partners can access the partner portal to do things like adding their business listing and any promotions, etc.- Mobile apps are built using flutter. I've dabbled with swift/swiftUI, kotlin, react-native, and flutter and today I prefer flutter for complex projects that I need on both iOS and android. Regardless of what path you choose, some tips I can offer when you're in the middle ground between a "this is more complicated than what's in the /examples folder" and "any top app that you use on a regular basis": • Spend a weekend going through the platform specific design guidelines. Open up your favorite top apps on iOS and android and use the same features on both. Notice the subtle differences. • Read the app store guidelines for both so you know what to expect. • Plan your application structure. What are the shared states, and how will you share data? Do you need to persist data on the device? What device permissions do you need to manage? What are the top level views? Do you need to make network calls? I used to never do this because I figured hey, its just a toy project!! But, as soon as that toy project turns into a passion pit, I need to make that new features can be added very fast instead of requiring a re-write. Just note the different moving pieces, and organize your code in a way that makes sense. • Nothing is perfect - flutter web is kinda meh and honestly I think its best anyway to just have separate mobile code, and web code.Learned a ton over the pandemic, hoping to put all of this to good use and keep learning. All the best!

7.Swift on Windows

I was skeptical of React native especially having tried it a few years ago, but new versions are incredibly nice.Plus, it’s running JS off thread. Performance has been fantastic. I rewrote recently an app in SwiftUI - the React Native app was faster and easier to write. Which was a surprise to me because I like the SwiftUI components more, but in the end the far superior hot reloading and far better dev tools, along with the much better flexibility (less time “getting the code/types to run”) meant I was moving about 5-10x faster.Finally, we are sharing almost 100% of code across native and web. We built a component kit designed to use react-native-web and that handles just a few edge cases, and the net result is quite awesome. We do obviously have it designed to look different when mobile, but it’s the exact same as the web responsive mobile. The web version adapts nicely based on screen size as well.So unlike Flutter you’re not having to deliver a massive web bundle with tons of incompatibilities and perf issues. And unlike any other language you’re fully cross platform.I ran it for the first time the other day on Android just to test if it worked and it did first try, no code change necessary. I’ve definitely changed my opinion - React is not just viable, but preferred to me, even if I could theoretically move as fast with a native app in each language.

8.Eight Years of GraphQL

I have yet to find an alternative to the GraphQL protocol that has the following requirements:- Good support for HTTP 1.1- Provides typesafe contracts for queries and mutations- Strong support for most common UI clients (JS/React Native/SwiftUI)- Backend can be written in a language that isn't JavaScript/TypeScript- Large developer communityClosest thing I've found is defining your schema using OpenAPI spec, and using tools to generate code from that source for the client and server, but this is a much worse DX than the process of defining GraphQL schemas.