Status: Deployed
Case Study: Last Action Note
A lightweight IntelliJ plugin built with Kotlin, designed to improve developer workflow through simple, context-aware action tracking.
links
4.4/5
Rating
None
IDE impact
~50ms
Load time
>1000
Active users
description
Last Action Note is a lightweight IntelliJ-based plugin designed to enhance developer workflow by introducing a simple yet practical capability—keeping track of recent actions in a way that reduces context switching and mental overhead. Built personal necessity, the plugin reflects a focus on utility, clarity, and seamless integration within the JetBrains ecosystem.
The project also served as a hands-on exploration of Kotlin and IntelliJ Platform plugin development. While the implementation remains intentionally minimal, it operates within a complex and rapidly evolving API landscape. This required working across both Kotlin and Java, adapting to shifting conventions, and reverse-engineering patterns from existing plugins and JetBrains’ own source code due to limited and often outdated documentation.
Despite these constraints, the plugin achieves a clean integration with the IDE, maintaining performance and responsiveness without introducing friction into the development workflow. Its simplicity is deliberate—prioritizing usefulness over feature bloat while laying a foundation for potential future enhancements.
Beyond functionality, the project represents a strategic step into the JetBrains plugin ecosystem and a broader transition toward Kotlin as a preferred language, highlighting adaptability and a willingness to engage with less-documented, real-world development environments.
screenshots
frontend
backend
data
third-party
other
challenge
The primary challenge was working within an under-documented and rapidly evolving plugin ecosystem, requiring reliance on source code exploration and adaptation to inconsistent or outdated resources.
conclusion
This project demonstrates the ability to deliver practical tooling within a constrained and complex environment, while quickly adapting to new languages and ecosystems. It highlights a focus on solving real developer problems with efficient, well-integrated solutions.
execution phases
#1 Idea & Validation
Identified a small but recurring workflow gap within daily IDE usage.
#2 Environment Setup
Explored IntelliJ Platform SDK and established plugin structure.
#3 Core Development
Implemented functionality using Kotlin with necessary Java interoperability.
#4 API Exploration
Navigated evolving APIs and limited documentation through experimentation and code analysis.
#5 Testing & Packaging
Validated plugin behavior and prepared it for JetBrains Marketplace distribution.