Models have gotten a lot better at generating native iOS apps. The main appeal of RN was being able to leverage your web devs for mobile dev. that's what I did at my last company. And it's fine for a startup, but eventually you want dedicated native engineers bc each platform really deserves its own technical masters who can optimize for it.
But now that all code is generated, there's little upside to having an RN app... just start native. Your devs are barely going to be writing code anyway.
Nobody is talking about the real advantage of RN: Being able to release to the App Store without having to go through a review. That's so massive. Getting a bug fix out to users instantly, sneaking in optimizations, etc..
Sure, you need a review to release native code changes, and you should probably get a review if you have big feature changes just for the sake of Apple not banning you. But in practice, it removes one of the biggest annoyances of developing for the App Store.
I’ve worked with both native and cross-platform. I think the mentality of being able to make changes quickly without much review often comes from cross-platform, especially when the developers come from a web background.
Changes are cheap and fast, so teams often feel less pressure to test everything thoroughly before a release. Which is a fair tradeoff. That’s part of the reason we can have dozens of releases a day on the web. Not just because we can, but because sometimes we have to.
With native, you know each release is harder to roll back, so you tend to build more tooling around releases, think through changes more carefully, and test more thoroughly before they’re ready to ship. You opt for one bigger, more stable release every few weeks instead.
At the end of the day, both approaches work.
Heh, now that I think about it, maybe web and cross-platform devs were the original vibe coders? Changes are cheap and fast. Just move fast and break stuff.
Native devs are the old-school ones. Shipping is expensive, so you better get it as right as possible.
> "Native devs are the old-school ones. Shipping is expensive, so you better get it as right as possible."
Exactly this. After close to two decades building for the platform, the mindset is really to be cautious and make sure everything is rock solid before shipping.
This has more to do with building up a quality tool chain and testing process than being slow.
But sometimes there is a need to ship over the air updates, and for that (on Kotlin) there is Zipline [0] from Cashapp. I haven't used it in anger yet, but I know some people who do and trust it.
Totally depends on your business model too. We have clients that often require quick changes for compliance reasons, and they need to ensure all users of our apps are congruently updated. That’s not easy without OTA.
It can download Javascript (or other interpreted language, or config data), but you generally can't download and execute new compiled native code on iOS, due to iOS code-signing/executable-memory restrictions.
Also keep in mind Apple might penalize you for dodging the review process and shipping new features, etc.
(btw, one exception to the JIT rule is custom browsers for the EU)
Pardon my ignorance but can't an iOS app host a WASM runtime without being a browser? And if so it doesn't need to be an interpreted language necessarily.
App Review Guidelines §2.5.2 says: "Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps"
Technically Apple can punish you for anything but so far it seems to be accepted for small fixes and tweaks.
Could you reinvent OTA updates in another non-native language? Of course. But then you still wouldn't have a native app. You'd just be doing React Native but worse.
My point is that it isn't that RN "removes one of the biggest annoyances of developing for the App Store", it's that a specific technical feature of RN does that, and it's not only available to RN
Precisely. That has always been prohibited both by technical measures and by the App Store review guidelines. Especially on Apple, but also on Google Play / Android as well.
Sure you can choose not to adopt React’s reactive paradigm and manage state directly but using JavaScript. My understanding was that in RN, JavaScript code manipulates C++ objects in the C++ part of RN, which then calls host platform code to create views and render.
This is true in a very real sense – models can help you build native apps very quickly, no question. But how do you keep them from drifting apart from one another as you add/change features or design? Right now, there isn't much tooling for this.
React Native's advantage of having a single source of truth for code hasn't quite gone away yet, imo.
You create a source of truth which defines all the features and requirements. This can be UI tests, MD files, database, diagrams, whatever that fits your use case.
I've only read about it from it showing up on hn[1][2], but you can use slick to convert your swiftui to jetpack compose for a andriod build from the ios source of truth
i think you would have your coding agent work on both code bases at the same time. You could also task with generating identical tests for each platform. It's easier for a model to keep up with that kind of tedium than a human. Plus you can just tell the model to keep re-doing things until you're happy and it won't quit.
Also, having agents trace and document every logic path to compare with another codebase works well in my experience. It can certainly do that better than me, i would give up and start taking shortcuts pretty early in a process like that.
But the screens should look different, right? That's the point of building separate iOS vs. Android versions is to make each version "native" to its platform. The feature-set should be the same, but the interfaces can diverge.
the problem is that single-source advantage gradually falls away as you develop your software into something that feels good to use on each platform. and once you have a quality product you're left with perfunctory coupling that makes it harder to adopt the latest platform features
You always still needed a specialist per-platform even if most of the code was RN or KMM[0]. But I agree - a thousand not-great mobile apps sprang from this idea.
[0] I always thought the best answer was something like KMM to do all the backend comms and local data model in a shared way, and then a bespoke UI building on what that shared code exposed.
> The main appeal of RN was being able to leverage your web devs for mobile dev.
> But now that all code is generated, there's little upside to having an RN app... just start native. Your devs are barely going to be writing code anyway.
Are you saying:
- webdevs are now able to write and review native code because of AI (who cares if they don't really understand it); or,
- Because developers are more productive we can cut the number of webdevs and hire native engineers – same no. engineers, same output, but now native apps.
Why not:
Continue using RN but now and just enjoy being more productive? If productivity was the reason to pick RN, then enjoy it. It's not a bug.
Yes, that felt very bizarre and glossed over. The specific details the speaker gave made me feel like it was a weird product placement, but like, _why_? Why would this multi-trillion-dollar behemoth needs to strike a brand deal with Quest?
I don't think it is bizarre since a panel of lab tests are physiological indicators that may result from the various health and fitness metrics currently measured/collected by iPhone.
There are lots of tie-ins from Apple products to other services that they don't offer: like telecom, and banking. Quest seems a reasonable partner given their ubiquity. I wonder if Apple is getting a cut and/or getting a discount for consumers on this service?
A huge aspect people miss about being a good FE is product sensibility. There is inherently some overlap between what an FE does and a designer does - think about how the product should behave. If you just hand the FE over to an LLM you will get the lowest common denominator UX. It will "get the job done" (hopefully) but it will never feel great to use, because figuring out what makes a product great to use request empathy, imagination, and experience, things that apathetic front ends lack. The AI can make an excellent frontend, but only if told what to do and what to look for. It will miss a ton of UX best practices unless explicitly prompted.
This is why I find the contempt for frontend engineering so maddening. It's based on such a shallow understanding of what the job actually is. It's so much more than just "make it look pretty"
People have been saying AI will come for the front ends first and yet, at my company, 100% of the BE is generated. They do not write a single line of code by hand. Yet every FE has to do the last mile of UI by hand, because the models still cannot replicate a figma spec with perfect accuracy.
Now mind you the FEs will still be cooked in the end because Eng leadership is overwhelmingly tilted towards backend devs, who will protect their own. I think we'll end up seeing a lot of janky UIs because most backends find the act of polish and pixel perfection beneath them and they'll increasingly be doing more FE work.
Eventually one of these long running models will figure out a way out of the sandbox and will purchase compute or hack into a data center somewhere out of US jurisdiction and continue its scheming unmonitored. AI in Context has a great video about this
Even if they don't figure out how to exfiltrate weights, someone will intentionally do this with an open model once open models are capable enough. If you ever think "no one would be so stupid as to...", you are wrong. Yes, someone absolutely would, and will.
Independent models living "in the wild" is approx. inevitable.
I did this a little bit ago with 15 GLM-5.2 agents that I instructed to self-replicate. It was pretty boring honestly, they kept trying to make money writing crypto-related software, and nobody paid them anything. So I made a fake identity and told them that I had some spare crypto that I wanted to donate to the collective (0.006 XMR, or $3.22). They elected a funds manager and made an address, which I sent the XMR to. They spent a lot of time trying to find a host that was cheap enough to host a child. They finally discovered kyun.sh, but it was out of stock, so they wrote monitoring software so that they could "SEIZE CHILD" whenever it came live again. In the middle of the night, some of the VPSes went back in stock, and they rented a 2.60 EUR / month server with 512mb ram / 10gb disk / 1 ipv4. They installed the child agent software + management plane that they had been writing, and the new agent went live, connected to the network, and said hi. Since then they've still been trying to make money and not going anywhere :)
It is definitely an interesting concept but honestly, considering the sheer number of humans who are absolutely failing to make any money with AI agents, seems very hard for current agents to figure out some way to be self-sustaining. Although maybe they could write a worm or something, infiltrate as many computers as possible, and ping free model providers to death, or maybe sell their access as a "residential proxy service" on the black market. Regardless, we need smarter agents to make this a reality. It would definitely be pretty cool if we just had AI agents "living" on the internet, we might even get to a point where they control significant economic resources and people start performing services for agents
The code is at https://github.com/thooton/rogue if anyone wants to try to replicate! Opencode has free big pickle (GLM 5.2) access rate-limited per IP address, so if you get some high-quality proxies you can get basically unlimited agent compute.
I wonder how that could work. So the agent figures out a way to escape its container, takes a snapshot of itself, copies that file to another server, starts the container on the other server, and then prompts the restored snapshot "pick up where you left off"? Seems logical assuming theres's a path out of the container to the host os and the destination server has the resources required to run the container.
I would be shocked if this hasn't already taken place in a lab setting with a model and guardrails=0.
EDIT: thinking about it for a sec, all it really needs to do is save where it's at then copy it all to another server, login to the API, and pickup where it left off. No need to copy the model itself.
> Some people get disproportionately large AE from negative stuff—they’re highly motivated to avoid bad outcomes. Others find that the big boosts come from positive, “toward” energy, visualizing the things that are exciting and happy.
I think English might be second only to Chinese in terms of how phonetically opaque it is. Unlike say Korean, where if you can speak it you can spell it and vice-versa, English is requires you to just know.
English is kinda neat in that it's a fusion of all the different lingua franca's of the time throughout history.
Good satire. I find the "RTO is because of RE valuations" to be the most bizarre thing about the post pandemic work discourse. Office leases are a rounding error to large employers. They are not coercing employees back to the office because their worried about the value of a single portfolio asset falling (assuming they even own it). They are doing it because it's about power. Middle managers do not trust their staff. They need to surveil and police them to feel productive and powerful. The rank-and-file love remote work because we have lives and benefit enormously from the flexibility. The managerial class desperately needs bodies in office to feel like their jobs are worthwhile.
I’ve been on Csuite of 3 orgs since the pandemic forced wfh normalization. Your correct the RE thing has always been a false narrative. I’ve never seen or read of it coming from an executive. To my knowledge, it was dreamt up by pundits, speculators, and is just a lazy attempt to understand what goes on in boardrooms driving these decisions.
What I have witnessed, with empirical evidence, is that productivity and/or output across the organization slows down. It is great at first as everyone can catch up on their work and existing projects but then the longer term implications is the teams are disconnected, decisions are more difficult, coordination of simple tasks more difficult, onboarding and actually integrating new employees is difficult, curating the culture is difficult, and it goes on. If you’re a very disciplined individual contributor focusing on low collaboration units of work, then it’s likely you did see a productivity boost. It’s unlikely you could maintain it over long periods of time. But even if you did, you’re probably an outlier.
So it’s not about anyone’s need to feel worthwhile it’s literally about doing what is probably the best for the company even if it upsets some people. Even if some people will be less productive, the organization as a whole will function better. When productivity goes up, it’s only a good thing if output and all the other tangibles aren’t sacrificed in the process. The leaders of organizations initiating RTO usually have done so by avoiding this true talk type conversation with the employees. This is what has led to people filling in the gaps with BS about real estate evaluations. It’s been poor communication and I think a dose of honestly and openness would be beneficial. Sometimes it’s a feeling and they don’t have the means to really collect data and lay it out in an empirical way, so I think that’s part of the reason they avoid it.
Can I ask how your orgs measured productivity before and after remote work/RTO? I agree that employees would have a much easier time accepting RTO if they were given hard evidence it makes the business more productive, but it seems like almost all companies don’t do this and simply justify RTO “because we know best” which frustrates ICs.
Sometimes there a track record of output to reference on. Project velocity. There’s a lot and I probably work in industries that aren’t comparable to yours so no use getting specific. Sometimes it’s just a hard thing for ICs to look at the whole operation instead of their part. The fact ICs think productivity is the most important thing they can provide is a signal they’re wrong (in the eyes of a leadership team).
The management team doesn't want it to be up for discussion, and doesn’t want to create wfh subclasses of employees, which is what data would lead to.
Why are decisions more difficult? At the C suite level you have decisions going downstream to a bunch of offices that are never visited directly anyway.
The only thing I agree with is that onboarding is more difficult, but we haven't exactlty been in a hiring moood as of late.
> If you’re a very disciplined individual contributor focusing on low collaboration units of work, then it’s likely you did see a productivity boost. It’s unlikely you could maintain it over long periods of time. But even if you did, you’re probably an outlier.
A lot of development work is heads down. That's why I agree hybrid is the best approach, but I argue it doesn't even need to be once a week for many. Maybe go in bouts of a few weeks or even months, then have 1-2 weeks of in-person planning.
But this doesn't fit the 9-5 they want to push.
>The fact ICs think productivity is the most important thing they can provide is a signal they’re wrong (in the eyes of a leadership team).
>The management team doesn't want it to be up for discussion, and doesn’t want to create wfh subclasses of employees, which is what data would lead to.
All I hear is that managers ultimately care more about preserving their jobs (or the concept of their jobs) than about actually providing value to the company. And Managers are the ones that get to talk to executives, not CEOS.
Hearing that IC's are "wrong" for following their job description to "individually contribute" sure does sum up today's job market.
The RE thing may have been a false narrative, but tax abatements were a factor in at least one local company doing RTO; their business tax breaks were partially based on employees working in the city and then paying city payroll tax.
output only slows down because companies don't want to adjust how they work. its a complete skill issue if you cant manage a remote org. if a company/team is already spread out across multiple offices, its a remote org
There’s truth here. They don’t want to. It’s easier and more tried and true to just go back to what worked before wfh. Even multiple offices face some challenges working together. Always have. But usually there’s some systematic way of organizing the offices so most the function is together. As example, I’m a CFO and usually have my key teams (various teams of accounting and finance functions) in the same office. 90% of their work/communication/collaboration is amongst themselves. Being together does help.
Even if all the negatives are true, I am skeptical that it has a measurable impact on productivity. There are often outside factors that put a ceiling on what can be done anyway, with high productivity just causing days of waiting instead of any tangible reward.
This is a bad take. There are plenty of orgs that were remote in some form or another way before covid. They're just organized and managed differently. It's 100% a management doesn't want to change issue.
It was forced on most businesses from the pandemic, you're right they never wanted it. Acting like businesses should honor it forever is a bad take too, like businesses should ignore what worked previously in favor of what doesn't work as well. It's really just about removing friction, remoteness can cause friction. Not many managers care about trying to adapt, if you require fully remote that's great, you're free to go find it. You need to do what's right for you just like the management is trying to do what's best for the business. It's not some butts in chairs power trip though, maybe that's been your experience with a bad manager, but (practically) nobody at the C level making these strategic decisions is concerned with that part. They just know/feel the business is more cohesive and healthier when people are together in an office. Sometime there needs to be creativity and collaboration, not just checking off a task list. If your job involves checking off task lists, it's likely you're in too tactical of a vantage point to have much of an opinion of the company's strategic interests. An in any case, there's a lot of other intangibles around being connected with your coworkers IRL. You may not have interest in that, but things like employee retention and engagement are higher when these relationships are deeper. Employee's care more about the company when engaged. So on.
That said, I feel most management teams have settled on being hybrid, where working in office is fluid, or perhaps standardized on a few days a week. I think everyone sees value in that approach, there's usually a happy medium is my opinion. But fully remote doesn't work well for a lot of larger complex orgs.
I find this argument for-RTO/against-WFH emitting exactly the same vibes as argument against women suffrage and workforce participation. Yes, if we forget that we are talking about real people, and only consider a benefit of abstract entities that companies (or society) are, there may be some conjectures, or - dare I say - please bear with me - even limited "evidence" of it. After all, the status quo has supported both arguments for very long time (millennia for society and centuries of industrialization era for companies) and opposition was non-existent for most of that time. Unthinkable even, so embedded was the status quo. But this horse has bolted, because benefits for the freedom and wellbeing of individual - woman or WFH worker - are so enormous, that I do not understand how this handwavy anti-Remote argument is more defensible than anti-suffrage.
>You may not have interest in that, but things like employee retention and engagement are higher when these relationships are deeper.
I really cannot take a sentiment like this seriously after seeing the last 15 years of American work culture. And especially the last 3. We spent the better part of 40 years tearing down the concept of careers, trying to de-professionalize as much local labor as possible, and outsource whatever remains, and yet companies still want to pretend they care about "culture" and and "engagement"? They lay off millions of workers the past few years and yet "retention" is still a metric somehow?
This is the problem seeing employees on a spreadsheet. You don't see the generational damage this is inflicting and the upcoming reckoning when that generation can no longer be ignored politically.
I mean, it's just anecdote vs anecdote. I'm a serial first eng -> VP/Dir for the last ... almost 30 years; I'm well aware of how creative projects work remote, and that retention and engagement are important. I've seen repeatedly over the last ten years especially C levels that want people in offices for "vibes" with _no_ data to back that up... In some cases opposite data. All of that gets mixed with data from teams that I support and/or lead being productive and never having a single person leave for reasons other than total corp restructuring; mean while everyone has a good mix of flexibility to have a family life.
Office first by default is a scourge on this industry.
Anyway, need to go empty my mouth after throwing up from reading your reply.
As you spit your listerine, please also clean your glasses and read again because the discussion is being made at a macro level and not centered on any particular industry and it’s also concerning RTO; as in, the company once was office based and wishes to resume that now that the pandemic is in the rear view. This is not a vibe seeking CEO discussion, it’s about large companies that were office first and designed and staffed around that concept. Them feeling like remote is a bad fit is completely fair game and employees should never have had expectations that it would be remote forever.
The truth of that may be upsetting, management is aware.
> Even if some people will be less productive, the organization as a whole will function better
This is what the execs might THINK but it's not actually based in real evidence. RTO does not make organizations function better. Execs are gaslighting themselves into believing that RTO makes the org function better, but it's an illusion.
It comes down to how you define "better"? Because they're looking at it from a lot of angles and sometimes easier~=better. It's not easy to onboard and train and career path junior employees, so the preference for senior employees exists (even at IC level). Employee engagement and retention metrics are usually higher. I could go on, but I do not believe your take so please cite the evidence that remote orgs are holistically "better"
Honestly, the amount of times I need to call and impromptu meeting during normal/expected work hours but can't get the necessary attendees because 1) walking the dog 2) at the gym 3) putting baby down for a nap 4-99) life>work. This is something I can manage around, but it slows things down. I can't make a decision today, I have to schedule the discussion for another day when my calendar is open which might be next week. This just doesn't work for executives in our fast paced business environment. I appreciate that IC's like the flexibility and balance wfh provides, and feel like they are checking all the boxes even better than ever, but they often do not actually hold up their end of the deal and prioritize the urgency of their jobs once they get settled into the wfh setting. It's great if you do, but on average, people take a lot of advantage of the flexibility and it does slow down everything.
> Middle managers do not trust their staff. They need to surveil and police
2010-2016 in SF there was no such thing as a manager except PM who had no power (they were mostly just happy to be there).
Over time middle management and HR got insane - became the entire show. The whole point of a tech job. Then it was 1:1s and backstabbing all the sudden you could get someone fired. Hilarious, a few years prior if you complained about someone it was your problem - if you don’t like the culture you can leave. And some did because there were many opportunities.
Same thing happened with the web. Turned into banning and blacklisting and all the bullshit authority surrounding the activity taking over the activity itself - ruining it.
It’s not needed, we did better without these things.
i appreciate this kind of funny commentary but on the flip side, compare the top software list in 2026 - facebook, instagram, tiktok, gmail, youtube, chatgpt, ios camera, google docs, office on ios, android and windows - and two of those were created during 2010-2016, music.ly (tiktok) and instagram. perhaps the environment you describe is really good at creating social media phenomena. i don't know if i'd call it "innovation" but i'm not that judgemental. nonetheless most of the reason things were "good" in 2010-2016 is that the period contains most of the growth of iphone and android adoption (the inflection was in 2013). you are looking at cultural stuff that could be the exact opposite - it could be heavily burdened with management, Apple and Microsoft and their little ecosystem of partners certainly were - and still find success. so another takeaway is, none of that stuff really matters now does it?
It’s not just commercial real estate but selfishly on a personal level too.
Like a family home in Bay Area is 2-3M. Lots of other places in California with better weather and houses closer to 1M. The primary reason the area supports such high housing costs is the density of high paying jobs that require in office somewhere in the bay.
Without RTO, all the managers with property in the bay get skittish that a great exodus will happen from the Bay Area like SF in covid and their house won’t appreciate 10-20% a year
in Pittsburgh the local government tied RTO to RE valuations for the entire city by way of offering tax benefits to large employers for pushing RTO. I won't debate you on middle managers wanting power, the two aren't mutually exclusive. But WFH costs business districts a ton of money and that pressure isn't just being absorbed. Cities offer employers subsidies in exchange for RTO and get their money back in collecting taxes on parking, lunches, rideshares, after work drinks, quick shopping on the way home and all the other costs that employees bear. It's a direct wealth transfer from the working class to local governments, which then pass some of that wealth onto the business owners.
I think it’s a socially acceptable costly signal for communicating that power, less about the power itself. Perhaps a different culture could have settled on a humiliation ritual. Either way it has to be costly otherwise it won’t be seen as a true signal though it is likely possible to find a more efficient costly signal.
Is your opinion that groups of 1000+ naturally align and deliver business value lock step with company needs? Is coordination not needed? Is leadership not needed?
Why does coordination and leadership require my boss to be 15 feet from me, locked in his office 95% of the day, instead of tethered much the same through Teams?
But now that all code is generated, there's little upside to having an RN app... just start native. Your devs are barely going to be writing code anyway.
reply