Here's a stupidly familiar workflow:
Someone sends you an image.
You download it.
Then you realize it's the wrong format.
So you open a converter.
Then the file is too large.
So you open a compressor.
Then you notice the image needs a few adjustments.
Now you're opening an editor.
Then you need to resize it.
Another tool.
At some point you're sitting there thinking:
“Bro… I'm just trying to process one image.” 💀
That annoyance is what eventually turned into APIC.
🛠️ I Didn't Start With “Let's Build An Image Editor”
I started with a much more boring question:
How many tools do I actually need to touch to finish one image?
The answer was… annoyingly high.
So instead of building another giant editor trying to compete with professional creative software, I went in the opposite direction.
Take the repetitive image operations.
Put them together.
Make the workflow stupidly straightforward.
That's APIC.
🧠 Think Of APIC As An Image Workbench
Not a Photoshop replacement.
Not a website full of random online utilities.
More like a workbench sitting on your Windows machine.
You bring an image in.
Then you decide what needs to happen to it.
IMAGE
│
┌────────┴────────┐
↓ ↓
MODIFY PREPARE
│ │
┌────┼────┐ ┌───┴────┐
↓ ↓ ↓ ↓ ↓
EDIT FILTER RESIZE CONVERT COMPRESS
│ │ │ │ │
└────┴────┴────────┴────────┘
↓
OUTPUT
The interesting part isn't any individual button.
It's the distance between the buttons.
🐕 Here's What That Looks Like In Reality
I took a normal image.
Nothing special.
Then started messing with it.
Brightness.
↓
Contrast.
↓
Shadows / highlights.
↓
Filter.
↓
Resize.
And suddenly the image is ready for whatever comes next.
No:
“Wait, which website did I use for this last time?”
No:
“Where's that converter?”
No:
“Which compressor doesn't destroy the image?”
Just the same application sitting there.
🔐 THEN I ASKED ANOTHER QUESTION
Why should a simple image operation require uploading the image somewhere?
That's where APIC's local workflow matters.
Your image is your data.
For the local processing workflow:
YOUR IMAGE
│
↓
APIC
│
↓
YOUR OUTPUT
Not:
YOUR IMAGE
↓
UPLOAD
↓
SERVER
↓
PROCESS
↓
DOWNLOAD
That distinction matters — especially when the image isn't something you want casually uploading to a random service.
⚙️ UNDER THE HOOD, THE PRODUCT ISN'T TRYING TO BE EVERYTHING
That's intentional.
I don't want APIC to become:
“The Ultimate AI Blockchain Quantum Image Superplatform™” 😭
I'd rather it become really good at the boring stuff people repeatedly need.
That's a much more interesting engineering problem.
How fast can the workflow be?
How clean can the UI stay?
How predictable should the output be?
How many unnecessary steps can disappear?
Those are the things I'm interested in.
🖥️ AND YES — IT'S A REAL WINDOWS APP
The demo below isn't a Figma prototype.
It's not a landing-page animation.
It's the actual APIC application running on Windows.
You can see the workflow happen in real time:
Open → Process → Modify → Convert → Output
And that's honestly the part I'm most proud of.
Because software stops being an idea the moment somebody can actually use it.
🚧 APIC ISN'T “FINISHED”
And I'm not going to pretend it is.
There are still things I want to improve.
Better workflows.
More processing options.
Performance improvements.
UI refinements.
More automation.
Maybe some completely different ideas later.
But that's the fun part.
APIC is being built in public, one version at a time.
🇮🇳 BUILT BY AKHOURI SYSTEMS
APIC is an Akhouri Systems project.
The goal isn't to make the loudest image-processing application on the internet.
It's to make one that quietly becomes the application you open when you think:
“I just need to fix this image.”
And then you're done.
🎥 Here's APIC.
No concept art.
No fake UI.
Just the actual application.
👇
APIC — Advanced Image Processing Center
🌐 https://github.com/Akhouri-Anmol-Kumar/APIC
💭 Now I'm curious:
What's the one annoying image task you still use a completely separate tool for?
Maybe that's the next thing APIC should solve. 👀
Top comments (0)