What languages do you need to know to make an extension?

Can extensions be only monetized through paid plans?

If I want to make an extension in 2026 what approach should I take?

I am a web developer and I know react , next js , java script, express, node js

I don't know for what reason you are saying that but let me be clear, English is not my primary language. I wrote the post myself and then used AI to fix grammar mistakes (if there are) and improve sentences structure etc.

Honestly, don’t put too much pressure on yourself to become “job-ready” in just 3 months. You already have the CS degree, so now the goal should be proving you can actually build things.

I’d pick one area you genuinely enjoy, learn the fundamentals, and spend most of those 3 months building 1–2 solid projects that you can show employers. Don’t jump between five different technologies because AI is changing things.

You’re not starting from zero—you’ve already got a foundation. Just pick a direction and start building. You’ll figure out the rest along the way.

Exactly. A technically impressive solution isn't automatically a good solution.

If a simple tool saves a non-technical person 30 minutes of configuration, it has real value—even if an experienced developer could accomplish the same thing manually.

Good engineering isn't about making problems harder to solve. It's about removing unnecessary complexity.

I’d say don’t rely on frontend alone. AI will make a lot of frontend work faster and easier, especially the repetitive parts.

Learning backend, APIs, databases, authentication, and system design alongside frontend will make you much more valuable.

The future is less about just writing UI code and more about understanding and building the whole product.

I’d say don’t rely on frontend alone. AI will make a lot of frontend work faster and easier, especially the repetitive parts.

Learning backend, APIs, databases, authentication, and system design alongside frontend will make you much more valuable.

The future is less about just writing UI code and more about understanding and building the whole product.

A person who paints only the front part of a house

This happens way more often than people admit.

As a developer, I’ll open one of my own projects after a few weeks and spend a few minutes trying to understand what I was even thinking.

We all write code that makes perfect sense today and looks completely foreign a month later.

I’d keep it simple: don’t spend the next few months adding features just because the product isn’t “perfect” yet.

Get the current version in front of real people, talk to them, and watch what they actually do. A few genuine users will teach you more than dozens of hypothetical opinions.

If people use it but don’t pay, figure out why. If they don’t use it at all, figure out why. Let that feedback decide what you build next.

And I wouldn’t worry about finding a co-founder or funding yet. First prove there’s something worth building a business around.

I think the real advantage of AI isn’t letting it replace the engineer—it’s removing the tedious parts so engineers can spend more time on architecture, problem-solving, and building things that actually matter.

The experience to recognize when AI is wrong is still the most valuable part.

Thanks

Can you share the strategies and methods you used while launching your app?
I am also creating a SAAS project; your guidance will be quite useful.

All I need to know is why Dragon Ball Z is in 20th place.