Marrakech, Beni Mellal, Safi: three labs, six notebooks, one PhD student on the edge. Three months later, his supervisor wrote to me to understand.
I met Yassine in October 2025, at a seminar held at the Aïn Chock Faculty of Sciences in Casablanca. He sat in the third row, taking notes at a frantic pace in a notebook that was already half-filled, his phone lying flat next to him because his fitness wristband had given up tracking the rate of his notifications. He approached me during the coffee break, between two industrial mini-msemen and an over-sweet tea.
"You're the one who built the PhytoNote app, right? I have a problem. I think I'm losing my PhD."
The multi-campus ATER profile
Yassine is a third-year PhD student at Cadi Ayyad University in Marrakech. His topic: the terpenes of Moroccan rosemary, Salvia rosmarinus (formerly Rosmarinus officinalis), with a focus on carnosol and carnosic acid. He'd been appointed ATER (a French-style adjunct lecturer position) for the 2025-2026 academic year. The job saves you financially, around 15,000 dirhams per month after tax, but it costs you in logistics. 192 teaching hours per year, spread across three sites: the main faculty in Marrakech city, the Beni Mellal annex, and the Safi university centre. Three different teaching teams, three distinct lab cultures.
On the research side, his PhD supervisor, Prof. El Mansouri, was asking him to keep running DPPH and ABTS assays on methanolic extracts from rosemary harvested in the Haouz region, plus a few comparative assays on Middle Atlas cultivars. Three host labs for these analyses, because no single one of the three campuses held all the equipment. The decent UV-Vis spectrophotometer lived in Marrakech, the microplate reader (a BMG Labtech FLUOstar Omega) sat in Safi, and his preferred Soxhlet extractor was in Beni Mellal. He rode CTM buses back and forth with his samples in a cooler bag at 60 dirhams per trip.
The chaos he described to me
His data lived in six places. Three physical paper notebooks, one per lab, never leaving their respective shelves. Two Excel files, one on the shared Marrakech PC that crashed once a week, the other on the Safi lab laptop he wasn't allowed to take home. A Google Drive folder synced manually whenever he remembered, mostly containing blurry photos of tubes labelled in Sharpie.
When he tried to cross-reference his DPPH results across the three sites, he spent his Sundays manually re-typing values from his notebooks into a master Excel sheet. Those Sunday transcriptions were where the errors piled up. An IC50 noted as 47 µM on Tuesday became 47 µg/mL on Sunday because he had forgotten to record the unit at measurement time. Three months later, his supervisor would ask him to recover the original unit and he couldn't.
I recognised that pain immediately. In my own first PhD year in Rabat, I lived the same dispersion between UM5 and an associated lab in Kénitra, and that's exactly the trigger that pushed me to code PhytoNote. Yassine was living the aggravated version of my 2023 problem: three campuses instead of two, plus a teaching load that saturated his week.
Setting it up
I installed PhytoNote on his phone (a Samsung A54, Android 14) that same evening, in the lobby of the Ibis hotel where he was staying the night. We spent two hours configuring his protocols. The YAML dpph_methanolic_v1.yaml for his standard DPPH• assays (final concentration 100 µM, HPLC-grade MeOH, read at 517 nm after 30 min dark incubation), another YAML abts_radical_v1.yaml for his ABTS assays (potassium persulfate 2.45 mM, read at 734 nm). We also set his five rosemary cultivars as presets, each tied to its Haouz GPS origin code so he would never again confuse one batch with another.
The feature that saved him, I believe, is the deferred sync. PhytoNote stores everything in a local SQLite database on the phone and only syncs to a server (his own, which we installed on a Raspberry Pi 4 at his supervisor's office) when wifi is available. No more dependency on Safi's flaky 4G, no more Google Drive crashes. And the export to Excel or a Pandas DataFrame happens straight from the phone in two taps.
Three months later, his supervisor wrote to me
Prof. El Mansouri emailed me in February 2026. She wanted to know "what I had done to Yassine". His results chapters, which she was reading to prepare his September 2026 defence, had suddenly become far more structured than those of the two other PhD students she was supervising. Every value was time-stamped, traceable to the extract batch, with experimental conditions attached as metadata. She could mentally reconstruct each experiment just by reading the exported Excel table.
Yassine had just submitted his first article to the Journal of Ethnopharmacology, on the comparative antioxidant activity of five Haouz rosemary cultivars. The paper was accepted with minor revisions in January 2026 and published online on 14 February. For an ATER scattered across three campuses, publishing in J. Ethnopharmacol during the third year of a PhD is not common. Most doctoral students in his situation end up postponing their defence by a year, sometimes two.
What it taught me
Yassine's story confirmed an intuition I had while coding PhytoNote, one I had never dared to say out loud. The tool is not magical. It does not do the science in the researcher's place. But it removes a layer of administrative friction that, for a geographically dispersed scientist, becomes the invisible limiting factor. Yassine did not become a better chemist by using the app. He just stopped losing six hours per week re-typing values into Excel and wondering whether his tube 47B held the Tahanaout cultivar extract or the Asni one.
This administrative friction, I know it well. I lived it myself, at a smaller scale. When I was assigned organic chemistry tutorials in second-year undergraduate during my own second PhD year, I thought I was going to have to abandon my bench work. I prepared lectures in the evenings and on weekends, I slept little, and my experimental data degraded in quality because I was recording it in haste. PhytoNote was born exactly from that moment, in November 2023, in the kitchen of my studio in Rabat, between two stacks of student papers to grade — the night of the botched DPPH plate. Yassine and I share the same November 2023 anxiety, except he lives the multi-campus version, and the app does its job.
He sent me a postcard from Marrakech in March, with a single sentence on the back: "Defence in September, you're invited." I'll be there, in cha Allah.
The technical detail of Yassine's multi-site setup (deferred sync to Raspberry Pi, DPPH/ABTS YAML for rosemary) is documented in the PhytoNote paper, section "use case 3: multi-campus ATER PhD student".