Switching to a standalone app helps me avoid that — fewer distractions, less wasted time. I’ve tried breaking the habit, but this is one reason I still prefer desktop version of the website.

What actually works is trunk-based deployments — keep main always deployable, and ship from there. Simple.

PRs, are underrated. They’re great for sharing context. You get inline comments, CI runs, you can test stuff in isolation by spinning up infra, and teammates actually see what’s changing.

Stacked diffs make juggling multiple PRs manageable. And yeah, PR reviews can slow you down, but honestly, I think that's a plus. Slowing down just enough to have another human look at the code pays off more often than not.

I think a lot of serious bird enthusiasts use this in the UK.

Here’s what worked for me:

Start with a solid project page – Focus on making your plugin polished easy to install and use via a project page. Good docs and instructions also drives search to your plugin organically.

Create useful content – Blog posts, guides, or even short articles that explain how and why you built the plugin something like behind the scenes. People read this stuff.

Use GitHub topics – Tag your repo well. People browse topics and trending pages. This is actually how one of our projects started getting noticed.

Submit to awesome lists – there are “awesome” lists related to IntelliJ plugins Java dev tools, AI tools send a PR to add your project. It’s a great way to get visibility among the right audience.

Be genuinely helpful in your niche – If your plugin helps with a common pain (e.g. repetitive Java boilerplate), hang out in relevant forums or threads (like here, Reddit, etc.). When you help someone, they’ll often check out your work.

See how it all goes and know when to move on, Good luck with your plugin.