8 comments

  • gregsadetsky 3 minutes ago
    Great work, thanks for sharing and congrats on the launch!

    Very very small note - many clickable things on your site (the "explore" and "new task" buttons, the directory and blog links at the top, etc.) don't change the cursor to the css "cursor:pointer" (ie the clicky hand)

    You might want to add `cursor-pointer` to your tailwind <button> elements

  • Bewelge 8 minutes ago
    Great job! If it's all on client you should make a PWA out of it so it can be installed and used offline.

    Built a client only webapp myself and offline usage is the main thing users ask about.

    • pratik227 7 minutes ago
      Yeah, I’ll do that. I have a Chrome extension that I’m planning to make paid, and I may also release a desktop version. I’m thinking of pricing it cheaply—around $2 for lifetime access
  • Antibabelic 24 minutes ago
    Doesn't a time-tested solution already exist in the form of PDF24?
    • zdc1 3 minutes ago
      Nice to have something that doesn't require Windows
    • pratik227 20 minutes ago
      It's not just PDF i'm also working on image processing and all as well
  • throwaway290 0 minutes ago
    makes it difficult to verify that it runs locally. important actions, like open a PDF, save edited PDF, will be stuck or error if you cut the internet after opening the site and only unstuck after you reenable internet.

    on first look it looks like it only fetches javascript but I didn't investigate. plus I don't understand why it needs to fetch JS every time even if I didn't reload the page

  • burgerone 24 minutes ago
    How does it compare to stirling pdf?
    • pratik227 21 minutes ago
      I’m doing everything locally, with no pricing on the extension for now. I do plan to make it paid later, but since all processing happens locally, your files never leave your device and remain completely safe.

      also not just PDF the image processing also WIP will be done by next week

  • TZubiri 22 minutes ago
    Might be better to provide a downloadable executable instead of asking the user to trust that the browser isn't doing what the browser was designed to do.
    • pratik227 20 minutes ago
      I plan to build a Chrome extension and am considering making it paid, around $2 for lifetime access. Also Desktop app is also good idea
      • niemandhier 2 minutes ago
        Extensions have the downside that a malicious actor can buy out the original dev and start using them as an intrusion point.
      • sabdarmdhn 16 minutes ago
        Make the Desktop Version natively, even tho its time efficient to make it just Electron
  • TZubiri 26 minutes ago
    Feels like infringing on the ILovePDF trademark. (Backpiggying on an established brand to make it look like you are affiliated, or the actual brand)
    • pratik227 23 minutes ago
      Ah, I’m not sure. I’m not directly using their name, and it’s not related, right? It shouldn’t cause any issues, correct?
      • franze 1 minute ago
        well you clearly state that your naming is based on their naming with this sentence "The Privacy-First Alternative to"

        even if it might not stand before court it is enough for a lawyer to write you a letter that is not 100% baseless.

  • 2Gkashmiri 39 minutes ago
    Oh cool.

    Can we add workflows to this?

    First merge all files then depending on output size compress to fit the size and other requirements?

    Or take out page 35, then compress rest

    Or extract page 2,5 and merge them and give me output withoit compress

    • pratik227 25 minutes ago
      Ah, cool idea. I’m currently integrating image processing features—crop, compress, and meme generation. Once that’s almost done, we can move on to integrating the workflow.