Open Request for Clarity and Stability in Kodular’s Future

Feedback
1

Dear Kodular Team,

I am writing as an individual developer who has been using Kodular. I have always appreciated Kodular as a platform that made app development accessible without needing advanced coding skills. It allowed me to experiment, build, and launch projects I am proud of. However, the situation today feels very different from when I first started.

Right now, using Kodular feels like paying rent to a landlord while also being required to pay electricity bills to someone else entirely. In practice, this means I am paying from multiple sides—monetization restrictions, or broken components—just to keep my apps running. This is frustrating, and I have to ask, should I continue investing my time, energy, and subscription money into Kodular, or should I consider moving away?

Community Feedback

I have been following discussions across forums, Reddit, and other Kodular-related platforms. Here are some real examples of what people are saying:

  • “Image gallery suddenly not working … after upgrade into Android 14 is not working anymore.” — Community Forum (Oct 2024)
  • “You just edit your target SDK to 32 and it will work … all problems solve related to permission denied.” — Kodular Forum (Mar 2024)
  • “The Kodular forum has become very quiet in recent months. Most people now realize that Kodular is over.”
  • “With every subsequent update, countless new bugs were added. I gave up trying to list them years ago.”
  • “Why are you charging $3.5 every month if you can’t update all your old codes and problems? … we are paying, but you are not working to improve all your components.” — Kodular Forum (Sep 2022)

These statements highlight a clear concern: many users are frustrated with broken components, lack of communication, and uncertainty about Kodular’s future.

My Experience

  • Built-in components often fail – Image Picker and other essentials frequently do not work.
  • Extensions fill the gaps – Independent developers provide solutions that Kodular itself hasn’t addressed.
  • Decline in active creators – Many users on the forums are no longer building but are searching for fixes or ways to migrate.
  • Subscription doubts – Paying for premium feels risky without knowing the platform’s long-term stability.

My Requests

  1. Remove dead components – Clean outdated or broken blocks to improve clarity and trust.
  2. Fix built-in components – Ensure core tools like Image Picker work reliably (especially on Android 13+).
  3. Collaborate with extension developers – Leverage the community’s proven solutions.
  4. Communicate openly – Be transparent about Kodular’s future, roadmap, and maintenance plans.
  5. Prioritize stability – Focus on making existing features dependable before adding new ones.
  6. Clarify subscription value – Make it clear what premium subscribers are paying for and why it’s worth it.

Closing

Kodular has been a fantastic platform for me and many others, but loyalty cannot survive instability and silence. I am asking honestly, will Kodular become a stable, developer-focused platform again, or is it time for me to consider moving on?

For context, even I recently experienced a problem right after the update: Error from Creator – apply to args. I know you are very busy fixing issues, but please count this request as important for your users.

Your transparent response will help me make informed decisions about where to invest my time and resources.

Sincerely,
Ibrahim Jamar

2 Likes
2

@Ibrahim_Jamar the same concern here. My huge project on Kodular makes me very stressed whenever I think about the Kodular future. I’m one of those who actually wants to pay for Kodular, but the issue is that monetization still hasn’t started there.

I don’t know what they are thinking. Right now, I feel so stressed. May be bad to mention but i need to know from @Diego “Does Kodular have a future?”

1 Like
3

I have also noticed that many developers in the community are creating extensions that fix the exact problems we face every day. In other words, solutions already exist — but Kodular itself never takes action to adopt them.

If fixing the old, broken components is difficult, then why not at least remove the dead components and officially integrate or purchase the working extensions from developers? This would,

Remove confusion for new users who waste time with broken components.

Strengthen trust in Kodular’s ecosystem, because the tools would actually work.

Support the extension developers who are already doing the work Kodular hasn’t been able to keep up with.

Right now, it feels like there is a huge gap between what the community has solved and what Kodular delivers. If that gap isn’t closed, then the platform will continue losing credibility.

1 Like
4

I do acknowledge the concerns, so let me address one by one first:

The only dead component as per my knowledge is OneSignal. We are working on adding a new one, but it’s currently tricky as it requires native Kotlin support.

We do have the fix ready to be released on the next update. And yes, we are fixing the bugs, prioritizing the most impactful ones first.

With this, are you referring to integrating extensions directly into Kodular Creator?

Agreed, and we have been doing that since the last few months already. More on this below.

Sometimes replacing an existing feature for a newer one is more beneficial. For example, OneSignal requires a complete rewrite and a new component.

Premium users get access to higher limits, that’s the main goal of Kodular Premium. Those funds are used to keep the platform running, just paying for its operating costs.

Now, addressing the general question on Kodular’s future:

We had a goal of convering Kodular into AI2. However, this was not as smooth as planned due to the codebase diverging that much. However, the promise of not closing Kodular Creator without a one-to-one replacement stays the same: projects will not be stop working suddenly without an alternative migration.

Our efforts, as of now, are in fixing bugs, and ensuring apps can still run on current and newer devices. Development of “new” features are being made to both AI2 and Kodular Creator, to ensure they are not throwaway work.
For example, you can find a major PR open to also support unlimited size projects in AI2, or to provide an alternative backend storage and be able to run AI2/Kodular Creator in alternative compute platforms.

If you want a clear answer to the question of whether you should move on or not, from my side I would say you can stay here. You can see through this year that many improvements in stability have been made, and our commitment with AI2 is still there.

3 Likes
5

Thanks @Diego I’m glad to hear that​:fire:

1 Like
6

Thank you for clarifying this, @Diego. I really appreciate your response. :folded_hands:

However, from a user’s perspective, it feels like there are more “dead” or half-working components beyond just OneSignal. For example,

  • Image Picker and similar media components don’t work properly on newer Android versions (13/14).
  • File handling and permissions are inconsistent, often requiring workarounds.
  • Some components behave differently than expected after updates, which makes them feel “abandoned” even if they are not officially removed.

So when developers like me say “dead components,” we don’t just mean completely removed ones, but also those that no longer function reliably on modern devices.

Thanks for the update, Diego. Glad to hear the fix is ready and that impactful bugs are being prioritized. Looking forward to the next update.

Yes, that’s exactly what I mean. Either integrate them directly into Kodular Creator, or make them free to use within Kodular. We’ve seen cases like the OneSignal extension — the developer already has it working, but instead of leaving it broken in Kodular, you could adopt or collaborate on it. This would solve problems faster and show that Kodular values community contributions.

It’s good to hear the clear assurance that Kodular won’t be closed without a proper one-to-one replacement. I also appreciate the transparency about the difficulties in converging with AI2, and the fact that bug fixing and stability are being prioritized.

That said, many of us still feel a bit uncertain. We really want to stay and support Kodular — even invest through subscriptions — but what we’re asking for is a stronger sense of stability and visible progress. If that continues, then your message gives us confidence to keep trusting the platform.

For now, I kindly request you to please prioritize fixing this issue,
Error from Creator: apply to args

From the day I first encountered it, I have not been able to debug my project anymore. It also causes the Companion to get stuck, which makes development almost impossible.

WhatsApp Image 2025-08-27 at 06.35.10
WhatsApp Image 2025-08-27 at 06.35.10485×1080 24.8 KB

Please consider this as a high-priority fix, because it directly blocks developers from testing and progressing with their projects.

Thanks

2 Likes
7

Hello, dear Diego.
Many people think like @Ibrahim_Jamar

Kodular is very valuable to us but it can return to its old days.
Extension developers used to develop components and features that didn’t exist in Kodular, making Kodular constantly dynamic. Now, we encounter numerous problems every day due to non-working components and library conflicts with Kodular. There are even plugin incompatibilities.
These situations are upsetting for everyone, they are not problems that cannot be solved, you are an experienced team.
Dear Kodular team :folded_hands:…

8

Adding one more point: A post about adding 2FA in Kodular was created 3–4 years ago, but it’s still not resolved.
Can you guys at least do your own product QA to verify whether your feature is working or not?
Please note, 2FA on your website is not working.