My perspective: I've been supporting and working with Mac and iOS developers since the last century, when Apple moved me from Chicago to be an evangelist at Apple HQ in Cupertino. I know as much as anyone about AI-assisted app development, as the creator/maintainer of the free/open source Axiom (https://charleswiltgen.github.io/Axiom/) for iOS/macOS devs.
It's not as dire as you might think. To software developers, the "AI revolution" is largely what the "desktop publishing revolution" was to designers. Yes, it meant the "riff raff" could theoretically play with the pros. Some percentage of the riff raff became pros. Most of the pros eventually adopted the tools and techniques used by the riff raff. Some of the pros didn't survive the transition and happily retired, taking their rubylith, Letraset type, and rubber cement with them.
The silver lining is that most of a software engineer's job isn't coding, it's thinking. LLMs can't do that, and we're not getting to AGI with current AI architectures. LLMs can amplify thinking, and an LLM in the hands of a software engineer or architect is at least two orders of magnitude more effective than it can be in the hands of a vibe coder. As LLMs get better for vibe coders, they also get better for pros.
One can argue that, by the end of the decade, hand-coded [your language of choice] may be considered as unnecessary as hand-coded assembly has been for decades. But coding in modern languages is already 7-8 levels of abstraction above the metal. One more level of abstraction is not the death of software engineering, IMO.
So a bit different from the other comments. We're a wearable company which of course pairs with an app.
We built iOS first because that's what most of our users have, though the team is mostly on Android.
We built our logic in Rust, so that compiles cross platform. It's really just the UI layer that is per platform.
Though I had initially written our first demo in React-Native, the team wanted to go with native UI.
Lately we've been talking about moving the timeline for our Android app up because we can get AI to help using the iOS app as a foundation.
I haven't seen anything really new and compelling in iOS/Android land. The promise of right once run anywhere continues to be a promise, and the bluetooth libraries across different devices (particularly in Android land) has me concerned.
I had a go at building both a Mac and iOS dictation app the other day (dictator.robgough.net) thinking that with Claude's input, this probably wouldn't work... but it was a real problem I had, and I wanted to see how far we could get. Best way to learn the tools, right? I'd already spent the day playing with alternative apps that didn't quite do what I wanted.
The app itself is fairly straightforward, but it included some intermediate complexity in terms of audio capture and calling local models. Both something I'd never done, and as not-a-mac dev something I probably wouldn't have attempted for a side-project while I'm meant to be bootstrapping my own thing.
I didn't touch a line of code, and I was blown away. I'm so impressed in fact that I'm predicting we'll see a resurgence in native apps in the near future. By far the worst (and slowest) part of the process is having to deal with the App Store, and the ridiculous hoops you have to jump through to get past review.
You need to have an Apple developer account. Then you need to submit your app to Apple for review. Then you need to comply with a list of sometimes arbitrary corrections/requirements that they send back (there is a document that specifies what you need to do, but it is not uniformly enforced in my experience). Then, eventually, you can list your app on the app store.
It’s not super onerous, but it is much more annoying than the theoretical alternative of allowing people to install software of their choosing on their hardware (i.e. download the binary and run it)
I suspect AI is going to result in the bottom falling out of the market for simple apps.
React made simple webapps a case of just gluing dependencies together and much more approachable to a generalist developer than the previous generation of web development was. But native apps weren’t affected in the same way. With AI I suspect we’ll see a lot of simple apps, the ones that really aren’t doing much other than CRUD operations on a remote API, become very heavily AI generated by generalist developers.
But there will still remain a healthy market for working on considerably more complex apps.
Will the complex apps be discoverable though, and if not, will the devs bother at all? I feel like this would be a win for old-school open source, where people would do it for the love of the aim, and better vetted app stores like F-Droid might win out
I don't install apps unless it's for an event or something. I just make my own to fit my needs. I can get a functional pwa out in about a day or two now.
I am building an app that is for a niche market, and I wouldn't have started without LLMs.
The hard part of this app is great design, requiring intentionally designed workflows and lots of real world testing. The code isn't the interesting part and now code isn't taking most of my time. It's great!
Once the design is nailed down and workflows tightened up, I don't expect much active development and can focus on distribution and marketing.
As a solo dev, this feels totally doable but ask me in 6 months.
My perspective: I've been supporting and working with Mac and iOS developers since the last century, when Apple moved me from Chicago to be an evangelist at Apple HQ in Cupertino. I know as much as anyone about AI-assisted app development, as the creator/maintainer of the free/open source Axiom (https://charleswiltgen.github.io/Axiom/) for iOS/macOS devs.
It's not as dire as you might think. To software developers, the "AI revolution" is largely what the "desktop publishing revolution" was to designers. Yes, it meant the "riff raff" could theoretically play with the pros. Some percentage of the riff raff became pros. Most of the pros eventually adopted the tools and techniques used by the riff raff. Some of the pros didn't survive the transition and happily retired, taking their rubylith, Letraset type, and rubber cement with them.
The silver lining is that most of a software engineer's job isn't coding, it's thinking. LLMs can't do that, and we're not getting to AGI with current AI architectures. LLMs can amplify thinking, and an LLM in the hands of a software engineer or architect is at least two orders of magnitude more effective than it can be in the hands of a vibe coder. As LLMs get better for vibe coders, they also get better for pros.
One can argue that, by the end of the decade, hand-coded [your language of choice] may be considered as unnecessary as hand-coded assembly has been for decades. But coding in modern languages is already 7-8 levels of abstraction above the metal. One more level of abstraction is not the death of software engineering, IMO.
So a bit different from the other comments. We're a wearable company which of course pairs with an app.
We built iOS first because that's what most of our users have, though the team is mostly on Android.
We built our logic in Rust, so that compiles cross platform. It's really just the UI layer that is per platform.
Though I had initially written our first demo in React-Native, the team wanted to go with native UI.
Lately we've been talking about moving the timeline for our Android app up because we can get AI to help using the iOS app as a foundation.
I haven't seen anything really new and compelling in iOS/Android land. The promise of right once run anywhere continues to be a promise, and the bluetooth libraries across different devices (particularly in Android land) has me concerned.
I had a go at building both a Mac and iOS dictation app the other day (dictator.robgough.net) thinking that with Claude's input, this probably wouldn't work... but it was a real problem I had, and I wanted to see how far we could get. Best way to learn the tools, right? I'd already spent the day playing with alternative apps that didn't quite do what I wanted.
The app itself is fairly straightforward, but it included some intermediate complexity in terms of audio capture and calling local models. Both something I'd never done, and as not-a-mac dev something I probably wouldn't have attempted for a side-project while I'm meant to be bootstrapping my own thing.
I didn't touch a line of code, and I was blown away. I'm so impressed in fact that I'm predicting we'll see a resurgence in native apps in the near future. By far the worst (and slowest) part of the process is having to deal with the App Store, and the ridiculous hoops you have to jump through to get past review.
could you talk more about the hoops? i’m getting close to the point i’d like to release something and it’d be my first time.
You need to have an Apple developer account. Then you need to submit your app to Apple for review. Then you need to comply with a list of sometimes arbitrary corrections/requirements that they send back (there is a document that specifies what you need to do, but it is not uniformly enforced in my experience). Then, eventually, you can list your app on the app store.
It’s not super onerous, but it is much more annoying than the theoretical alternative of allowing people to install software of their choosing on their hardware (i.e. download the binary and run it)
I suspect AI is going to result in the bottom falling out of the market for simple apps.
React made simple webapps a case of just gluing dependencies together and much more approachable to a generalist developer than the previous generation of web development was. But native apps weren’t affected in the same way. With AI I suspect we’ll see a lot of simple apps, the ones that really aren’t doing much other than CRUD operations on a remote API, become very heavily AI generated by generalist developers.
But there will still remain a healthy market for working on considerably more complex apps.
Will the complex apps be discoverable though, and if not, will the devs bother at all? I feel like this would be a win for old-school open source, where people would do it for the love of the aim, and better vetted app stores like F-Droid might win out
>Will the complex apps be discoverable though
That is the real issue. How to get noticed in a sea of slop.
I don't install apps unless it's for an event or something. I just make my own to fit my needs. I can get a functional pwa out in about a day or two now.
I am building an app that is for a niche market, and I wouldn't have started without LLMs.
The hard part of this app is great design, requiring intentionally designed workflows and lots of real world testing. The code isn't the interesting part and now code isn't taking most of my time. It's great!
Once the design is nailed down and workflows tightened up, I don't expect much active development and can focus on distribution and marketing.
As a solo dev, this feels totally doable but ask me in 6 months.
I'm have a game on both app stores, built in .net Maui. It earns enough to keep a roof over my head.
AI is useless when developing with Maui, as it's too new of a development framework for any AI's knowledgebase to have a clue what to do with it.
https://github.com/dotnet/maui/wiki/Using-AI-to-Work-on-.NET...
I’ve been thinking about this—if I wanted to learn iOS dev where should I start? (Book preferred.)
Mostly for fun/scratch my own itch, and using AI as a companion/helper device.
It is bad. Layoffs everywhere. Google is becoming apple. Companies want you to do the job of 6 engineers using ai.
The market is saturated for new apps.
I’ll be curious to see how many new vibe coded apps make it to a 2.0
It's incredibly easy to make apps nowadays, it's all about distribution (usually on social media).