Live data from Hacker News

Ask HN: What Is the State of App Development in 2026?

news.ycombinator.com

81–90 of 91 posts

Re: Ask HN: What Is the State of App Development in 2026?

#81

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. L…

why was your team against react native? (for mobile app right that goes along with the wearable right?) you can ship the actual UI stuff in seconds. you can write your own plugins for anything native and just call it. we have a app that uses many native SDK calls which we write plugins for and call. not to mention that once the native work is done you can deploy ui level changes and new features, bug fixes to users o…

I've used react native a bunch. When you've got custom elements it isn't always the cross-platform write once you think it is. I've always had custom components across iOS and Android.

The big complaint is that the amount of work to get the level of polish needed in premium apps just isn't there. Or you need to do a bunch more work and it isn't significantly different than the amount of work of getting a native iOS and native android dev.

Re: Ask HN: What Is the State of App Development in 2026?

#82

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,…

[flagged]

Re: Ask HN: What Is the State of App Development in 2026?

#83
post #6

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…

I mean, in general I dislike some of the more extreme app store gating.. but if apps are getting vibe coded with little effort I think gatekeeping is more important than ever. I think "is the author willing to put in the work to pass review" might be a useful heuristic, and it could also prevent things like vulnerable software being published. Plus it amuses me to imagine big tech having to deal with the slop apocaly…

My problem with the gatekeeping is that it isn't applied fairly. It's a central control point where a government can put pressure on the gatekeeper to suppress undesirable content. Plus, there are billions of people in the world who cannot qualify for Google's latest guidelines for becoming a registered developer. My team's app https://www.appdevforall.org/code-on-the-go/ is about empowering those people and if sideloading goes away then they won't be able to build and share the apps they need.

Re: Ask HN: What Is the State of App Development in 2026?

#86
From my perspective biggest shift is that people that would never have made anything digital 10 years ago are now making their own apps and websites. It is cool to see because often they make things that currently do not exist. The downside is that we software people that have been in the trenches for a while also learn about laws, cyber security and other topics that you should know, but claude won’t tell you unless you know what to ask for. These people have never heard about any of these things, and what I have seen so far getting built ranges from slightly risky to straight up super illegal. All without no clue what they are doing, no warning from claude, and the timeline from zero to launching something illegal can now be done by the average person in an evening.

This is both good and bad. We get more new stuff, people enjoy creating these websites, but they risk themselves and others people in the process. Like a kid being allowed to drive a partly autonomous car.

The super annoying thing I have encountered are managers and other low technical people with some influence over engineers that now believe they ”know the limitations of AI” because they managed to make a CRUD demo in 30min. More than once have someone in my vicinity expected claude to one shot an algorithm that might be physically impossible to even do. I have also seen people try to ”prove” that it is possible by having claude make this algorithm on some toy example where the output looks okay at first glance, but with no verification that it is actually correct. And now the engineers ”just need to take it to production”. AI have made any professional software development 100x worse in my experience. Annoying people that previously could be convinced that certain things are not quick and easy are now extra stubborn, extra annoying, extra time consuming to deal with. Therefore, in my professional life, AI is a big net negative when it comes to efficient use of time. AI made all bad things worse, and barely brought anything good with it. I am convinced that it doesn’t have to be like this, but most organizations are dysfunctional to some level, and that just became worse. If I could go back in time, I would not have gone into software engineering. I love the field, but there is just too much BS going on.

I also see and hear about tiny teams being more effective than ever, teams that already have the skills to know what they are building, and how. They can ship more, faster, and still ensure reliability because they know what they are doing, and they are allowed to spend the time if needed to ensure things are done correctly (without AI powered ”managers” standing in their way).

I think we will see many small companies literally come out of nowhere, no funding, no big names behind them and completely crush companies 1000x their size because of AI. I also believe big slow organizations will use AI to become less efficient and ship worse products while panicking on their way down, ensuring ”all in on AI” by sending more emails faster than ever.

More easy problems will be solved than ever, every imaginable easy problem will be possible for anyone to solve. The hard novel problems will remain unsolved, remain difficult and only the smartest, most stubborn, most stupid people will attempt to solve them, and if they do, the market will reward them.

Re: Ask HN: What Is the State of App Development in 2026?

#87
post #10

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…

These kinds of apps are basically a spreadsheet. The same way anybody can whip up an adhoc spreadsheet without being a programmer, financial analyst, or anything in particular this will enable similar adhoc for many applications outside of the Excellike GUIs of the world. In many ways, this is all that’s needed to unlock a huge opportunity for individuals to build their own tools, just like they have with spreadsheets. But it also means the risk inherent in this type of paradigm is large, just like it is with spreadsheets. But, I think we shoulder the risk. Maybe we find ways to reduce it or put other governance in place. But it’s too big of a super power to ignore and be completely risk adverse. Spreadsheet errors have crashed the markets in the past but I guarantee their use has not diminished and I guarantee there and trades being made a this moment based on formula errors and the magnitude just happens to be smaller so we collectively tolerate it an accept it as part of the process.

Re: Ask HN: What Is the State of App Development in 2026?

#88

Earlier quoted context omitted.

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.

Complexity doesn’t matter. Nobody jumps on the App Store and thinks, “I’m going to install something complex today.”

Presumably complex problems are lacking solutions and if that requires a complexity to solve, people will discover it. Not because it’s complex, because prior solutions were lacking.

Re: Ask HN: What Is the State of App Development in 2026?

#89
From my recent engagement on social media and in developer communities, these are the top things that I could come across: 1. On social media, people are mostly talking about getting approval for the App Store or the Play Store, rather than how they built their app, its structure, or the problems. 2. On social media, they are talking about promoting and marketing their app, whether it is a mobile app or a web app. I guess this thread is about a mobile app. 3. In developer communities, it does not matter anymore. You give them a problem, and they will come back with an application for it. For people who are early in their career, they are far from knowing even Git. There are keys publicly mentioned in their GitHub repository, and the code structure is nowhere to be present. On the other side, when I talk to tech teams through developer communities, for a lot of them who have adapted AI very well, they seem to be in heaven because they are working on multiple threads together. A lot of people have created a workspace where frontend and backend code is edited by agents that are hierarchically distributed across. I think shipping is getting faster and faster, and obviously the feedback loop has also multiplied, owing to more bugs to be fixed.

When I mention developer communities, I have my platform with more than 300,000 people signed up on it, so you can consider my experience to be valid

Re: Ask HN: What Is the State of App Development in 2026?

#90

Earlier quoted context omitted.

why was your team against react native? (for mobile app right that goes along with the wearable right?) you can ship the actual UI stuff in seconds. you can write your own plugins for anything native and just call it. we have a app that uses many native SDK calls which we write plugins for and call. not to mention that once the native work is done you can deploy ui level changes and new features, bug fixes to users o…

I've used react native a bunch. When you've got custom elements it isn't always the cross-platform write once you think it is. I've always had custom components across iOS and Android. The big complaint is that the amount of work to get the level of polish needed in premium apps just isn't there. Or you need to do a bunch more work and it isn't significantly different than the amount of work of getting a native iOS a…

[deleted]
Post reply on HN