JuiceSSH – Give me my pro features back

Original Article ↗ Hacker News Discussion ↗

Loss of JuiceSSH Pro Features & User Impact

  • Multiple users report previously purchased Pro features (especially port forwarding and cloud backup/sync) no longer work, or the app asks them to pay again.
  • Some who repurchased at higher prices were immediately locked out or saw no benefit.
  • Plugins required separate Play Store APKs that are now delisted, further degrading functionality.
  • JuiceSSH itself appears delisted for some users; others still see existing installs but with broken backend services.

Rugpull, Exit Scam, or Just Neglect?

  • One side calls this a “rugpull” / “exit scam”: lifetime purchases no longer honored, price increases, backend shutdown, and no communication or refunds.
  • Others argue it looks more like abandonment or life changes rather than intentional fraud, noting the app’s many years of solid service.
  • Some commenters looked up the developers’ current corporate roles and criticize them for not wrapping things up responsibly (refunds, open-sourcing, or unlocking Pro for all).

Alternatives to JuiceSSH

  • Termux is heavily praised: full Linux userspace, built‑in ssh/rsync/editor, free, and works well with custom keyboards and widgets for one‑tap SSH/port‑forward scripts.
  • ConnectBot, Termius (local use free), and Serverbox are cited as good SSH clients; several users say they “never looked back.”
  • On iOS, multiple SSH/terminal apps are said to surpass JuiceSSH; some switched platforms partly for better app quality.

Android Terminal & Virtualization Discussion

  • Android’s new “Terminal / Debian VM” (Android 15+) is discussed: full Debian in a VM, but heavy, flaky, and limited to certain devices/SoCs and pKVM setups.
  • Comparisons: Termux runs directly in Android userspace (with unusual paths); optional PRoot “fake chroot” is slower. The VM approach avoids old host kernels but is laggier and less stable for now.

Security & SSH Key Management

  • Broken cloud backup prompts concern over old keys still stored remotely. Some advise rotating keys and moving to modern algorithms (e.g., ed25519).
  • Strong opinions:
    • Private keys “should never leave the device” vs.
    • Having distinct backup keys and multiple client devices as a practical compromise.
  • Debate over encrypting keys with passphrases: helps but still vulnerable to offline attacks if passwords are weak. Suggestions include SSH certificates, hardware tokens (YubiKey/TPM), and agents to reduce passphrase typing.

Refunds, Google Play, and Ownership

  • Several users report failed refund attempts due to Play Store time limits (e.g., 48 hours or 120 days).
  • Some mention using chargebacks via credit cards but fear (or report) Google retaliating by locking accounts.
  • Examples of other purchased apps being sunsetted (games bought by large companies and removed) reinforce worries that paid apps are effectively rentals.

Patching, Sideloading, and Piracy Ethics

  • The blog’s smali patching is appreciated as a “classic cracking” throwback; some suggest tools like ReVanced/Morphie as general patching workflows.
  • Ethical split:
    • One camp says patching out Pro checks is justified since users are merely restoring what they paid for.
    • Another argues it’s still piracy; the proper path is refunds, reviews, and migration to alternatives.
  • Concern that stories like this may be used to argue against sideloading; others counter that closed ecosystems are exactly why users need the ability to patch/escape.