Video summary

Using reMarkable Pro at Work - Compared to Using a Boox Tablet

Main summary

Key takeaways

Technology

Tech focus: reMarkable Pro “for business” vs Boox (Android-based)

Collaboration / business purchasing model (reMarkable)

  • reMarkable positions the product as a business/team collaboration platform and offers bulk purchasing bundles (for large teams).
  • Account/device limits: only 3 devices per account, so team scaling is constrained.
  • Collaboration limitations: the speaker can’t find a way to share notebooks jointly (e.g., real-time “joint notebooks” are not available).
  • Meeting sharing options (limited):
    • Share a page in meetings
    • Share your screen
    • Email notes as a PDF
    • The workflow is criticized because meeting notes require manual emailing/addressing, rather than a more modern UX like typing a name and getting auto-suggestions from contacts.
  • Business security + Connect for Business (planned/preview):
    • Mentions data security and that business hosting is “hosted by Google.”
    • A “Connect for business beta” is planned/rolling out to more users.
    • Example shown: “31 active seats” (suggesting scalable collaboration seats), though the speaker says it remains unclear how collaboration will work in practice.

Real-world “work” workflow the speaker uses (personal note-taker)

The speaker uses reMarkable Pro for:

  • Desk note-taking (video ideas, content strategy, ongoing work)
  • Personal planning (2-week planner and school-day planning)
  • A workflow of starting from PDFs, annotating them, and keeping quick side notes

They compare it to an Android “daily driver” (a Boox mini model), emphasizing cross-platform and cloud-based continuity.

Why Boox/Android is presented as better for collaboration (speaker’s core argument)

Cross-platform collaboration advantages (Android + app ecosystem)

The speaker argues collaboration is “streets ahead” on Boox because it’s full Android, including:

  • Google Play Store access
  • Ability to use Android apps directly (e.g., Microsoft 365/OneNote, Word, Teams, messaging, cloud storage apps)
  • Ability to log into separate personal vs. work accounts (separate instances)

They add that collaboration isn’t limited to annotations—one device can operate across the same cloud/app environment the team uses (Microsoft cloud, Google cloud, etc.).

Security framing (Boox/Android managed environment)

For work contexts, the speaker claims security is strong when devices/app access are controlled via:

  • Microsoft cloud + Microsoft InTune badged work profiles
  • Google Play Protect security posture for Android

They note that for ultra-sensitive/government environments, teams may already use organization-managed devices.

Shared real-time notebooks on Boox (claimed feature/limit)

The speaker states Boox can support:

  • Up to 10 books/devices on one account
  • Real-time notebook collaboration across those devices

They also mention the ability to log out/in between personal and team accounts when needed.

Meeting integration capabilities (Boox)

The speaker says Boox fits more meeting-room setups because it can do more than “companion device” tasks:

  • Access to microphones/speakers and Bluetooth
  • Screen sharing
  • Use meeting apps (implied: Teams/Excel/other productivity apps)

They emphasize that Boox can use many apps in their full form, not only “PDF in/PDF out.”

reMarkable Pro integration limitations (major critique)

“True integrations” vs PDF/markup workflow

The speaker argues reMarkable’s integrations are often PDF-based and not live:

  • Word/PowerPoint/Chrome integrations work mainly by sending content as PDF for markup, then emailing it back.
  • In contrast, Boox/Android can work on live files and use apps normally.

Media handling: no direct image insertion

A specific missing capability is highlighted:

  • reMarkable can’t drag/drop or insert JPEG/PNG into notes
  • They suggest workarounds (e.g., using PowerPoint “send to reMarkable”)

The speaker finds it odd given the device has color e-ink but lacks basic image paste functionality.

Cloud/file workflow friction (Google Drive integration issues)

Issues described include:

  • Integration can become limited/incomplete (earlier versions had indexing problems; the speaker claims later versions improve)
  • If Google Drive permissions time out, the user may need to delete and re-add the integration
  • Export formats exist (PDF/PNG/SVG), including scaled vector graphics (SVG) useful for artists, but:
    • Export path/folder selection is limited (exports to the root and requires manual moving)

“Unfinished” workflow complaint

The speaker dislikes needing a second device to manage versions, move files, or store/read content live, calling the experience “unfinished.”

Handwriting recognition + UI behavior note

  • Handwriting recognition is described as a professional feature that can be “not too bad,” even with tools like a paintbrush.
  • However, edits can trigger new page versions, requiring re-recognition.
  • They compare this to Supernote’s workflow (described as better, though not the focus of the video).

Reading/display comparison (bonus: comics/eBooks)

  • The color e-ink experience is described positively: the display looks good and “closer to the real thing,” but not perfect.
  • Criticism:
    • The device isn’t compatible with certain comic/e-reader formats (they reference CBR)
    • The speaker ends up relying on PDF comics

Final positioning conclusion (as presented by the speaker)

reMarkable Pro is framed as

  • Excellent for distraction-free personal/professional note capture
  • A periphery/companion to laptops/phones
  • Best when collaboration needs are mainly review/sign-off workflows (documents sent to a leader for annotation)

Boox (Android) is framed as

  • Better for true team collaboration due to:
    • Android app support
    • Cloud/app ecosystem compatibility
    • Meeting-room and multi-app workflows
    • (Claimed) real-time collaborative notebooks and multi-device team limits

Main speakers/sources (from the subtitles)

  • The primary speaker appears to be a single reviewer/host (uses “I” throughout; no named co-speaker).
  • References are made to:
    • “professional people” / “professionals” (unnamed group)
    • “professionals who tell me” (unnamed; anecdotal evidence)
  • No explicit named on-screen source is clearly identifiable from the subtitles.

Original video