Pockit
100% Client-side Web Tools. PDF, JSON, Dev Utils & More.
22 followers
100% Client-side Web Tools. PDF, JSON, Dev Utils & More.
22 followers
100% Client-side Web Tools. Secure, Fast, and Free.Stop uploading your sensitive files to random servers. Pockit allows you to process data directly in your browser. It includes a PDF Editor (Merge, Split, Sign), JSON Formatter, JWT Decoder, and 30+ developer utilities. Zero latency, zero privacy risk.
@hobbada How does Pockit ensure compatibility across different browsers and devices?
@masump Since Pockit is built with React 18 + Vite, it handles most cross-browser compatibility issues out of the box. I also used Tailwind CSS to ensure it's fully responsive, so it should work smoothly on your phone, tablet, and desktop! 📱💻
I personally test heavily on Chrome, Safari (iOS/macOS), and Firefox. If you spot any weird bugs on a specific device, please let me know—I'd love to fix it! 😊
One feature I really poured my heart into is the Cmd + K (or Ctrl + K) command palette. ⌨️
Since there are over 50 tools, I wanted navigation to be instant without touching the mouse. Could you give it a try and let me know if it feels snappy and intuitive? Your feedback on this specific feature would mean a lot to me!
@hobbada
Building a 100% client‑side, all‑in‑one tool suite is incredibly smart—it solves both the privacy anxiety of uploading sensitive files and the frustration of switching between different slow web tools. The PDF + JSON + JWT utility combo is exactly what developers and privacy‑conscious users need.
A strategic question: As a free, privacy‑first toolkit, are you primarily targeting developers and technical users, or are you also seeing interest from non‑technical professionals (like freelancers, marketers, or students) who need quick, secure file edits without installing software?
(I ask because I specialize in helping productivity and developer tools connect with both technical and broader professional audiences on LinkedIn—where discussions about privacy‑friendly workflows, developer utilities, and no‑install tooling are happening daily.)
@olajiggy321 Thank you so much for the insightful feedback! You nailed it—solving that 'privacy anxiety' was my main motivation.
To answer your question: I initially built Pockit for developers (like myself), which is why I focused on JSON/JWT tools. However, I'm definitely realizing that the PDF and Image tools have a much broader appeal to freelancers and students who value privacy.
I haven't explored the LinkedIn audience much yet, but that sounds like a huge opportunity. Thanks for the tip!
@hobbada
Thanks for the reply, HK! That's exactly what I've seen—developers discover tools like Pockit for the technical utilities, but the privacy‑first PDF/image tools have massive appeal to the broader professional audience.
On LinkedIn, you could run two parallel campaigns:
Technical audience: Targeting developers with the JSON/JWT/utility angle
Broader professional audience: Targeting freelancers, students, marketers with the "private, no‑install PDF/Image editing" message
The beauty is they're the same product, just framed differently for each audience. I've helped similar tools execute this dual‑audience approach.
If you'd like, I can sketch out what those campaigns might look like. Feel free to connect on LinkedIn or share an email where I can send over some ideas
@hobbada
Hey HK, circling back. Had a quick thought—I mocked up what two LinkedIn campaigns—one for developers (JSON/JWT tools) and one for freelancers/students (PDF/Image tools)—could look like for Pockit. Happy to share it over email if useful. No call needed—just something to glance at.