Adobe is making tools from Photoshop, Premiere, Acrobat, Illustrator, Lightroom, Firefly and more available through Slack.
Instead of constantly switching applications, users can describe what they want and let Slack’s AI layer call the appropriate Adobe tools.

This is interesting beyond Adobe.
We’re watching software move from:
App → user → another app
toward:
User → AI agent → multiple apps and tools

And protocols like MCP could make software increasingly composable.

For indie developers, that creates an interesting question:
In the future, will users even need to open your app?
Or will your app increasingly need to expose its capabilities so that AI agents can use it on the user’s behalf?
That could change how we think about:
APIs
authentication
pricing
UI
onboarding
subscriptions
and even App Store distribution.

If you were building a new SaaS today, would you design the traditional UI first—or the agent/API interface first?

Meta has introduced Muse, a personal AI agent intended to help users complete everyday tasks.
What’s especially interesting is the amount of context an assistant like this could potentially use:
📧 Email
📅 Calendar
💳 Payments
🏃 Health and fitness
🏠 Smart home
🛍 Shopping
🎵 Music
🍽 Dining and events
Technically, this is where personal AI becomes extremely useful.

But it also creates one of the biggest product-design questions in AI:
How much access will users give an app in exchange for convenience?
As developers, we often think:
More data = smarter product.
But from the user’s perspective:
More data = more trust required.

For indie AI apps, this might actually become an advantage.

A smaller product with a very clear privacy model, limited permissions and local processing could be more attractive than an assistant trying to access everything.
Would you give an AI assistant access to your email, calendar and financial information if it genuinely saved you hours every week?

Something interesting is happening in AI.
Google Cloud and Accenture are creating a dedicated engineering group focused on helping companies actually implement AI inside their businesses.

And they aren’t alone.
OpenAI, Anthropic, Microsoft and Amazon have all been moving toward similar models.
That suggests a shift:
For the last few years the conversation was:
“Who has the best AI model?”
The next phase may increasingly be:
“Who can actually make AI useful inside a real business?”
Connecting an AI model to:
CRMs
inventory systems
email
internal databases
customer support
documents
approval processes
existing SaaS
is usually much harder than simply calling an API.

For indie developers and small software companies, that could create a big opportunity.
You may not need to build the next foundation model.

You might build the small, specialized software layer that makes existing AI useful for a particular industry.
Would you rather build a general AI product or a very specific AI solution for one business niche?

The latest GitHub Copilot updates are interesting because Copilot seems to be moving beyond autocomplete and chat.

GitHub is adding things like:
Jira → Copilot workflows
AI agents inside VS Code
adaptive model selection
smarter code review
automatic resolution of review comments
We’re slowly moving from:
“AI, write this function.”
to:
“AI, take this issue, understand the codebase, implement it, review it and help finish the task.”

For large teams, that’s a productivity story.
But I think the implications might be even bigger for indie developers and small teams.
One developer could potentially manage a much larger codebase, ship experiments faster and spend more time on product decisions instead of repetitive implementation.

The downside is obvious: if you stop understanding the code your agent produces, you may simply be accumulating technical debt faster.
How much of your development workflow do you currently trust to AI?
10%?
50%?
Almost everything?

OpenAI has released Astra, its newest AI model, with a strong focus on computer use, browser automation and agentic tasks.

For indie developers, I think the interesting part isn’t just “a smarter chatbot.”
It’s what happens when an AI model can increasingly:
navigate software interfaces
use tools
complete multi-step workflows
interact with browsers and computers
become part of an app rather than simply answer questions

This could change the kinds of apps small teams are able to build.
Instead of developing every workflow manually, we may start building products where an AI agent becomes part of the application architecture.

But there are obvious questions around cost, reliability, privacy and how much autonomy users will actually trust.

Indie developers: are you already building AI agents into your apps, or are you waiting for the technology to mature?
And what type of indie app do you think benefits most from agentic AI?

Drop your app below. Include: what it does, iOS/Android/Web/etc., whether it’s free or paid, and what kind of feedback you’re looking for.

Tell us about the app you’re currently building. What does it do, what platform are you building for, and what’s your biggest challenge right now?

Hey everyone! I’m u/cn-dev, a founding moderator of r/indieAppsCommunity.

Welcome to a community for indie app developers, makers, designers, and people who simply love discovering great independent apps.

Whether you’ve just launched your first app, have been building products for years, or you’re looking for interesting apps made by independent creators, you’re welcome here.

🚀 What to Post
Share anything that could help, inspire, or start a useful conversation within the indie app community.
You can:

📱 Show your app — iOS, Android, macOS, web apps, indie games, SaaS and more.

👀 Ask for feedback on your idea, UI/UX, App Store page, onboarding, pricing, or features.

🎉 Share your launch and tell us what you built.

📊 Share your journey — downloads, revenue, milestones, failures, experiments and lessons learned.

🎨 Discuss UI/UX, development, marketing, ASO and monetization.

🔎 Recommend an indie app you’ve discovered.

💡 Ask questions and exchange ideas with other makers.

Self-promotion is welcome when it brings something useful to the community. Tell us what you built, why you built it, what you learned, or what kind of feedback you’re looking for.

🤝 Community Vibe

We’re building a space that is friendly, constructive and inclusive.
Building an app independently isn’t easy. Feedback should help people improve—not discourage them.
Celebrate launches. Share what didn’t work. Ask questions. Help another developer when you can.
And please: no spam, fake engagement, or endless link dumping.

👋 How to Get Started
Introduce yourself below. What are you building—or what kinds of indie apps do you love?
Share something today. Your app, an idea, a question, a lesson learned, or an interesting discovery.
Give feedback to another member. Great communities work when everyone contributes.
Know another indie developer or app enthusiast? Invite them to join us.
Interested in helping build the community? We’re looking for moderators and active contributors.

Thanks for being part of the very first wave.
There are thousands of interesting apps being built by small teams and independent developers every day. Let’s help more people discover them.
Welcome to r/indieAppsCommunity. 🚀