Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Swift SDK for Android

swift.org

Post reply on HN
Print view View original

181–190 of 298 posts

Re: The Swift SDK for Android

#181

Post by makeitdouble »

xethos wrote: post #167
makeitdouble wrote: post #162

Earlier quoted context omitted.

Average amount of money spent means little in the context of parent's comment (revenue for a US company). For instance, if you're Netflix, do iOS user bring you more revenue in the US ? What if you're Hertz ? What about Walmart or Costco ? The only factor will be how many of your users are on iOS vs android. It's a different story if you're a gaming company and target whales of course.

Even if you're a social media company, where network effect is everything and getting into everyone's pocket matters , you can still go iOS first. Snap ran with that strategy at first, and it hardly killed the company. Notably, that's a situation that actually matters for cross-compatibility. There's no web client for SnapChat. Hertz & Costco could point Android users to the web with few repurcussions, IMO

This is still about the actual market share. iOS being 55%+ of the market makes that strategy viable in the US. You'd start with android instead if you were to launch in Korea for instance.

Re: The Swift SDK for Android

#182

Post by lenkite »

ls-a wrote: post #40

Thank you. Please kill RN and Flutter already. I'm done with square UI apps that handle touches after two days

> Please kill RN and Flutter already.

Just No. Nobody will kill >30% of apps on the iOS store. Flutter is simply a massively superior development experience overall compared to the horrifying disaster that is SwiftUI. SwiftUI is so utterly pathetic that more than a third of all apps are now being written in Flutter.

"The compiler is unable to type-check this expression in reasonable time" -> one of the most atrocious and common errors that increases cortisol levels and reduces life expectancy amongst mobile developers.

Please kill SwiftUI already. For the sake of Humanity.

Re: The Swift SDK for Android

#184

Post by tcoff91 »

cosmic_cheese wrote: post #173
tcoff91 wrote: post #171

Earlier quoted context omitted.

Xcode is dogshit though… I’m mostly in Neovim writing typescript (react native) luckily.

I've not had much trouble with Xcode in the past 15+ years I've been using it. Its biggest warts involve Interface Builder, which is easily avoidable by using code for UI instead of XIBs or storyboards. With Android Studio, I'd say the ways that it being an IntelliJ IDE puts it above Xcode are cancelled out by other aspects of Android development, which can be abysmal. Swift Package Manager and Clang/llvm code stripp…

Gradle is the single most confusing build system tool of all time. It’s so bad.

I agree that other than JetBrains everything else about it sucks ass.

Re: The Swift SDK for Android

#185

Post by [deleted] »

palata wrote: post #87
trevor-e wrote: post #47

Very excited to see this as an official project! I've been toying around with multiplatform frameworks like RN and Flutter for a side project of mine but they never feel right. I'd rather use the native UI per platform and have a nice way to share business logic. KMP exists but I think for most developers wanting to build an app it's more common to build for iOS first, and then port to Android later if the app gets t…

> KMP exists but I think for most developers wanting to build an app it's more common to build for iOS first This sounds US-centric to me. The advantage of KMP is that it is pretty mature and it is used in big apps like Google workspace (Google Docs etc), so it feels like it may be in a really good position. I used to be exited about Flutter when it started, but the speed of major releases (by the time I had rewritte…

[deleted]

Re: The Swift SDK for Android

#186

Post by noduerme »

throwup238 wrote: post #174
noduerme wrote: post #170

Earlier quoted context omitted.

I guess I'm not clear on what you mean about putting business logic in the client. It can't only be on the client side. If you do so, then obviously you have to replicate it on the server to check that the client was sending the right results, no? Not to mention avoiding thread races and double inserts and whatever else may have gone stale on the server before you allow a client to validate something? Even if your co…

That’s the exact opposite of what the GP is suggesting. Read this again: > Business logic is the real killer. Have one person suck it up and do it in typescript (sorry y'all) on the GQL/apollo server and all the clients can ingest it easy. Move the logic to the GQL retriever so that clients don’t have to implement business logic.

Yeah, I understood what they said. I'm wondering why the previous owners of the code decided to put business logic in the client.

Re: The Swift SDK for Android

#187

Post by mk89 »

featherless wrote: post #57

Does this result in the Swift code being compiled or transpiled?

It's compiled.

From what I see in other threads, skip.tools offers the possibility to transpile SwiftUi to Compose, so you build one UI and port it to android too.

Here we're talking about sharing the code logic (written in swift) and write android UI that uses it.

Re: The Swift SDK for Android

#188

Post by realusername »

rustystump wrote: post #128
bsimpson wrote: post #86

The most important question for every cross platform framework is what happens to the UI? Adobe products (both the Creative Suite, and their Flex Builder environment for Flash app) had their own design system that felt foreign on every platform it shipped on. If you wanted something that felt native, you had to reimplement e.g. Apple Aqua in Flash yourself. Flutter goes out of its way to do that work for you, aiming…

Very unpopular opinion but i like apps that ashew looking “native” for an original ux. Maybe it is my love for gamedev and all the crazy designs they come up with but i personally loath boring uninspired native apps esp when the native ux is terrible. Apple wants everyone to conform because historically their ux is on point but the last update really reinforces my view.

The debate has been settled anyways, none of the top apps (Facebook, Whatsapp, Youtube, Tiktok..) uses the native design, users simply do not care.

Re: The Swift SDK for Android

#189

Post by nicce »

mosura wrote: post #37

I hope they actually stick with this. Swift embedded, for example, is a sort of proof of concept more than viable platform, and you end up battling that more than the problem you are trying to solve. It is a shame because aesthetically Swift is easily the nicest of the modern safe languages, but there have been really odd noises in the community about project leadership that sour things.

> Swift embedded, for example, is a sort of proof of concept more than viable platform, and you end up battling that more than the problem you are trying to solve.

Yet Apple has managed to create WatchOS. I don’t know what is the portion of Swift, however.

Re: The Swift SDK for Android

#190

Post by realusername »

lenkite wrote: post #182
ls-a wrote: post #40

Thank you. Please kill RN and Flutter already. I'm done with square UI apps that handle touches after two days

> Please kill RN and Flutter already. Just No. Nobody will kill >30% of apps on the iOS store. Flutter is simply a massively superior development experience overall compared to the horrifying disaster that is SwiftUI. SwiftUI is so utterly pathetic that more than a third of all apps are now being written in Flutter. "The compiler is unable to type-check this expression in reasonable time" -> one of the most atrocious…

Having worked with Flutter, I also have the same opinion, I don't think you could pay me enough to use xcode and care about all these half documented apple frameworks.

The app build and upload process is painful enough as it is, I don't want more of it.

Post reply on HN