PaperTrail for iOS/iPadOS (1.4.4 released; in-place Bike/OPML roundtrip!)

PaperTrail 1.3.1 released!

Bug fixes only until Autumn.

Current totals

  • known bugs: 0
1 Like

1.3.2 released

I’ll post the detailed changes later on, but I received an email about one minor issue to do with archiving behaviour, and the tests added for that fix have helped increase the hardness of the app in numerous places: move, delete, sort, indent, outdent, and duplicate.

changes:

  • Archiving completed tasks while viewing a saved search or filter now adds them to the existing Archive section instead of creating a duplicate
  • Archiving no longer accidentally sweeps unrelated tasks into the Archive
  • Archiving a completed task now keeps its notes and sub-tasks together with it
  • Move to Project now works correctly when used from a search or filtered view
  • Delete with Children no longer removes unrelated tasks when used from a search view
  • Sort Projects and Reindent now apply to the whole document from a filtered view, rather than affecting only the visible items
  • Indent, Outdent and Duplicate now affect only the intended task and its real sub-items when used from a search view

PaperTrail 1.3.3

  • add: Swipe to indent/outdent :smiling_face_with_sunglasses:
2 Likes

PaperTrail 1.3.3 (380)

Now available.

1 Like

I’m interested in using the testflight release combined with the bike 2 preview. Is it possible to transparently use PaperTrail on bike files or does it always involve an export?

I understand that the latest version is always on the App Store. Right now I get broken files when opening a .bike file created with the v2 preview and just save it. The resulting file can’t be opened neither by bike on macos nor by PaperTrail on iOS anymore. Am I doing something wrong?

Experiencing same behaviour here.

Thanks for the reports, I’ll make repro and fix a priority today!

Latest is sometimes on TestFlight, but currently latest is release.

Edit: the issue here is a gap in my thinking. Bike is meant as import/export only right now, I but I neglected to realise that they also qualify for a lossy load path. Apologies, will fix ASAP.

@rcvdio @Hickz can you please confirm which bike format you are using? v1 or v2? .bike (html) or .opml?

OK, this is fixed. Submitting new build.

Bonus!

  • full write-in-place .bike and .opml
  • no need to export
  • just open-edit-close

:smiling_face_with_sunglasses:

Will be 1.4 as I think it’s now a Big Thing

It’s the v2 .bike files for me.

1 Like

Currently the roundtrip can load v2 or v1 bike files, but will write out v1 files. For a number of reasons. These will still load into bike v2.

I will try to improve this going forwards, time permitting.

1 Like

PaperTrail 1.4

  • released
5 Likes

I love it! Thanks a lot.

2 Likes

Thanks for the positive vibes!

I’d like to encourage anybody that loves my app to leave a review on the App Store saying so.

(Don’t tell them I sent you! LOL)

1 Like

Hi there, I’m a long time user of TaskPaper since 2008 and I’m a heavy user as well. I’m using it for almost everything. I tend to have “big” files like 780 KB of 12’000 lines and using it with TaskPaper on osx is blazing fast. I’ve been waiting for a TaskPaper ios replacement for quite a long time and recently Jesse told me about PaperTrail. I’ve immediately bought it. The UI, functions are super great but there’s one major drawback: performance. With most of my 700 KB, it lags with my iPhone 11 under iOS 18.7.2. Is there something that would cause these lags, in scrolling and especially searching within my file. It’s impossible to work that way but I believe this is something that could be fixed considering the very nice foundation of the application.

1 Like

Hi Nicolas, @nicolasbulb

It depends on the structure of your file. The good news is if I can reproduce the hot spot then I can make some changes to improve things.

You can generate a one-way scrambled debug version of a file by long-pressing the Settings button on the toolbelt. (FWIW I cannot unscramble it because I do not have access to the scramble key generated at your end.)

There have been several improvements over the past year for different types of large files, most recently files with many levels of nesting. So I’m hopeful your type of file will help me improve the app.

(Architecturally, PaperTrail is quite different to TaskPaper. Something I’m thinking about for a v2.)

Can anybody help me repro the issue @nicolasbulb is describing? My 10,000 lines synthetic file full of TaskPaper tags doesn’t show any such issues.

Hi again @nicolasbulb

I’ve resolved the search slowness, I am now debouncing after each character is typed, so that the search only fires/updates after you stop typing. This makes a difference for everybody, but will more visible older devices.

Testing shows improvements in searching between 2.3× and 4.4× with some related features speeding up 5.3×

Thanks for the report! I’m still interested to look into your scrolling issue but I will need a sample doc to do that.


PaperTrail 1.4.1 (383)

  • change: search now applies shortly after you stop typing, rather than re-filtering on every letter
  • fix: lag when searching or filtering very large documents (10,000+ lines)
  • chore: add a 12,000-line stress-test document and performance benchmarks for large-file search

1.4.1 released

Hopefully we will hear back from Nicolas at some point.

is this normal? Exporting from Bike 2 and Bike 1; once as .md file the other one as .bike file.
Bike 2 and Bike 1, Papertrail 1.4.1, iOs 26.6, iPhone15 pro max, MacbookAir m4, Tahoe 26.5.2


thanks

If you mean “is this expected”, the answer is yes.

Bike files contain a lot of hidden data.
TaskPaper and Markdown are plain text.
The hidden data has to go somewhere so is stored as frontmatter and special tags. If you take a look at Bike markdown it’s similar.

PaperTrail isn’t meant as a Bike replacement, but offers the ability to open and save Bike files if you need to edit them in a pinch on your iPhone.

1 Like