TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

I'm Sticking with Native iOS Development

35 点作者 riveralabs大约 1 年前

9 条评论

pzo大约 1 年前
I&#x27;m doing the opposite even though been ios dev for a decade and now learning react &#x2F; react native. Reasons: - golden days of mobile apps are gone, these days less and less people download apps<p>- it is more important to have desktop &#x2F; mobile web app these days<p>- pwa and mobile apps and tech are slowly getting good enough<p>- if you are native ios or android you are limiting your jobs and business opportunities - native mobile dev is like niche inside niche these days. Probably half of jobs is typescript&#x2F;javascript&#x2F; python related.<p>- in current market and ai landscape your have to prototype and ship fast to be competitive even at the cost of slighly worse UX
评论 #40369898 未加载
评论 #40369434 未加载
评论 #40369503 未加载
评论 #40369556 未加载
yatz大约 1 年前
Unless you are in the business of building apps for others, in my experience, cross-platform development rarely works. The amount of time you spend on implementing platform-specific conditional logic, dealing with UI latency, additional debugging time due to cross-platform masking actual errors, and above all keeping your codebase in order, outweighs the benefits by a huge margin.<p>The team that originally started might do a decent job but over time new people come on board, deadlines and other challenges make people start cutting corners and making design choices inconsistent with the original designers leading these codebases to become unmanageable.<p>What can work with some serious dev team discipline is to build common frameworks that you can use cross-platform and never dare to attempt cross-platform user interfaces.
refulgentis大约 1 年前
For what it&#x27;s worth, economically for an individual, it&#x27;s sort of the reverse in my experience. I feel like I snuck into Google in ~2016 because pure-iOS is so rare. I only had 1 out of 7 interviewers who worked on iOS, 2 who had tangential brief experience, 4 who had never used it. Also, Swift was new, so the people who <i>did</i> know iOS couldn&#x27;t really speak to it when I used it to write code.<p>If I&#x27;m launching a product, I&#x27;m doing Flutter. To me, it&#x27;s Swift but with no rough edges. Most importantly for a product, it lets me maximize leverage and get cross-platform. The performance is really astonishing compared to my days with React Native, it&#x27;s native in that it&#x27;s not being JIT&#x27;d.<p>But if I&#x27;m happy with a nice gig &#x2F; set of consulting clients doing iOS, that&#x27;s great, probably can do that until the end of time. I think we&#x27;re seeing the first wave of startups doing Flutter to maximize engineering leverage, but long-term, it&#x27;s too divisive to have a singular Flutter codebase for most large businesses. They&#x27;ll specialize.
flax大约 1 年前
I understand the author&#x27;s point, sticking with what&#x27;s comfortable and working.<p>In a sense, I&#x27;m doing the same thing, but what&#x27;s comfortable and working for me is Flutter. I don&#x27;t have any Apple devices to develop on (but I do have a work macbook, and can borrow my wife&#x27;s iPhone), so to target iOS at all, I vastly prefer cross-platform. Apple still makes that artificially difficult in many ways. You can&#x27;t even upload a build without xcode (mitigated by codemagic.io). My distrubution certificate recently expired and I spent a lot of time on the Apple connect site before realizing there&#x27;s no way to request a new certificate without using Apple tools that only run on Apple hardware. It should be a button in the same UI that shows the certificate!<p>Anyway, without cross platform tools like Flutter, I wouldn&#x27;t target iOS at all. Apple just takes every opportunity to try to leverage you into their ecosystem, and I&#x27;m not going to do that.<p>And now that the WebAssembly target is officially supported, maybe I won&#x27;t bother anymore.
airstrike大约 1 年前
IMHO SwiftUI is so good, no amount of describing its greatness can do it justice... you have to try it to really understand it
评论 #40369826 未加载
评论 #40370639 未加载
akmarinov大约 1 年前
Cross platform does seem to be slowly eating away at native apps - if you look at a lot of big companies out there, all of them use cross platform - like GM uses React Native for their car apps, Microsoft uses it in their Office Suite, Skype, Amazon, Shopify, Walmart, Tesla and many many more.<p>It seems that if you play at scale and are a big company - you&#x27;re pretty much on React Native or maybe Flutter though that doesn&#x27;t make a ton of business sense imo.<p>I wonder at what point Apple looks at things and wonders why they even bother investing so much in Swift and SwiftUI. At which point they&#x27;ll either<p>1. Leave it to dry on the vine<p>or<p>2. Go the other way and put in a &quot;no cross platform frameworks&quot; in their developer agreement and force companies to use native code.
munchler大约 1 年前
I think this is a niche of a niche of a niche, but it’s interesting to see the creative decisions young developers are making to carve out a sustainable career. I hope this path works out for you!
评论 #40369501 未加载
moribvndvs大约 1 年前
That’s great for you. I don’t have the resources to build the same app from scratch for three different platforms at the same time.
giantg2大约 1 年前
Isn&#x27;t <i>true</i> native iOS development objective-C?<p>But yeah, this article is basically the same for me, only I&#x27;m an Android dev. I don&#x27;t release anything on iOS. I probably would if it wasn&#x27;t for that $100&#x2F;year Apple dev fee. My stuff is free, so why should I pay Apple such a high fee. If I did write for iOS, I&#x27;d probably do Swift or SwiftUI at first to learn it. Then maybe I&#x27;d look at a cross-platform framework.
评论 #40369375 未加载