Zapply: The Desktop Revolution Continues

Remember when we pivoted Zapply from a cloud-based SaaS to a scrappy, unstoppable desktop app? Turns out the pivot was just the beginning of the adventure. Since rolling out the concept, we’ve been knee-deep in the unglamorous but vital process of turning our “Desktop for Everyone” dream into reality—installers, certificates, OS reviews, auto-updaters, the works!

The Install4j Bullet Train

Desktop software distribution isn’t always straightforward—ask anyone who’s tried to package a cross-platform Java app. We tested a bunch of solutions, but eventually found our best friend in install4j. Yes, it’s pricey for an indie budget, but they offer a 90-day free trial that’s saving our bacon right now. And honestly? It’s worth it.

• Installers for All – Windows, Mac, Linux—one tool to build them all.
• Smooth UI – Doesn’t feel hacky or slapped-together, which is crucial for user trust.
• Auto-Update Support – We wanted a frictionless user experience, so we integrated auto-updates from the get-go.

Our MVP is all about user trust, so nice, clean installers are a must. While some folks can handle a .jar or some arcane command lines, we wanted Zapply to feel as polished as any enterprise app.

SSL Certificates & The Joy of Red Tape

Of course, you can’t just spin up an installer, stamp your name on it, and call it safe. Welcome to the bizarre world of code signing certificates. We wrestled with SSL.com to score legit signing certificates for Windows—so your OS won’t throw scary “Unverified Publisher” errors. This also meant:

1. Crunchbase Profile Updates – Because apparently code signers want to confirm you’re a real business. We had to refine our corporate presence, lock those profiles, and ping Crunchbase multiple times.

2. Identity Shuffle – SSL.com loves verifying every snippet of your identity. We swapped emails, docs, verifications, and probably half our sanity just to get that sweet .pfx file that Windows trusts.

Mac? That’s Apple Developer territory, so we’re twiddling our thumbs a bit while the Apple Developer review gods decide our fate. Once that stamp of approval lands, Mac users can install Zapply free of those ominous “Unidentified Developer” warnings. Fingers crossed—there’s no messing around with Apple.

Hidden Magic Under the Hood

While the code signing and installers hog the spotlight, so much more is bubbling beneath the surface:

• Auto-Updates – Because we’ve all lived through “Please uninstall your old version before installing the new one.” No, thanks. We integrated auto-update, so Zapply always runs the freshest build. Minimal user hassle, maximum developer agility.
• Modern UI – If you thought Java desktop apps were stuck in 2002, say hello to FlatLaf. We’ve got a crisp, modern interface plus dark/light themes, so users can pick their vibe. Eye candy meets productivity—a must for indie software in 2025.
• Spring Boot on Fly.io – Our Zapply backend is chugging along on Fly.io because the “run it anywhere, scale as needed” approach fits us like a glove. The desktop app talks to our Spring Boot REST API for user data, tracking, subscription checks, etc. No cloud-based bot headaches, just a friendly database and some microservices.

One Critical Step Left: Auth

The last big puzzle piece? Authentication. Before we roll out those job-hunting autopilots, we need secure login flows. We’re testing a few approaches—JWT vs. OAuth vs. magic links—while keeping it as frictionless as possible for the user. Once we have auth locked and loaded, we can finally dig into the actual MVP features: letting Zapply do its job-application wizardry locally, while our backend quietly watches your subscription status and metrics. No more big server loads or suspicious IP addresses. Chef’s kiss.

Where We’re Headed Next

• Finish Up Auth – The biggest showstopper right now. Then we can unleash real features.
• Get Apple’s Blessing – Once that’s in, Mac users can install Zapply without a fuss.
• Refine the UX – Because if we’re saving people from job application drudgery, the UI better be polished enough to make them smile.

Then it’s MVP time—actual end-to-end usage, real feedback, and the next wave of iteration. The best part of building a desktop app that talks to a minimal backend? We’re not burning cash on ephemeral cloud browsers, so we can iterate, pivot, break stuff, fix stuff, and keep overhead near zero.

Final Thoughts

This entire journey—from pivoting to a desktop app, to code signing chaos, to Apple dev purgatory—might sound insane for an indie project, but that’s the hustle. It’s not just about writing clever code; it’s about dealing with all the behind-the-scenes logistics, so your users experience something magical and seamless.

As we always say: Shipping is the only truth. The pivot to a desktop approach is paying off huge right now—lower costs, fewer bot detection nightmares, and more control for power users. Next up, we wrap up auth, polish the final bits, and let Zapply fly.

Stay tuned—once the dust settles, the next wave of updates will be all about real-world usage, scaling, and maybe that sweet, sweet job-offer automation. We’re pumped. You should be, too.

Zapply—it’s not just a pivot; it’s a revolution in job-hunting automation, right on your desktop.