Think about a data science assignment: there's the problem set PDF, a couple of markdown notes, and a short Python analysis. Or a biology lab, with a protocol, an annotated paper, and some quick calculation off to the side. In practice all of those pieces end up scattered across a PDF editor, a notebook site, a notes app, and wherever your file manager dumped the download.
Native .ipynb support is my attempt to pull that back into one place. You can create a Python notebook from the same +New menu you already use for notebooks, whiteboards, folders, and PDF imports, and it lands in the current folder right next to the rest of the assignment, not off in some separate developer corner of the app.
And it's a working notebook, not a preview. Lectra edits code and markdown cells, runs Python, captures the output, and holds state between cells. I'm not trying to turn the iPad into a desktop IDE. I just want the small bits of code that show up in actual coursework to feel like they belong with the reading and the annotation and the notes.
The editor details are where a notebook either feels real or feels fake, so those got attention too: Python syntax highlighting, auto-indent after a colon, keyboard shortcuts for running cells and moving between them. Little things, but they're what keep it from feeling like a text box pretending to be a notebook.
It's not finished. Notebook thumbnails still need their own look, deleting a notebook should clean up the files underneath it, and there's more to add. But the base is there now, and that's what I was after: PDFs, notes, whiteboards, folders, imports, and Python notebooks all sitting in one Lectra library.