Change log
Newest first. Each entry names the app version it shipped with — desktop and phone are versioned separately, and changes to this website are marked site. The app shows its own version at the top-left of the page.
desktop v1.32.1
Until now every edit on the desktop opened a banner under the header (Unsaved changes — will sync shortly, then Saving changes to Drive…) and closed it again a few seconds later, so everything below moved down and back up each time. The sync status now lives in a small chip on the header line, next to the ☁ Google-account chip, in a slot that never changes size: ✓ in sync, unsaved (click it to sync at once), saving… — the chip pulses gently while the upload runs — and back to ✓ in sync. The banner with its Sync now button still appears for the two situations that need a decision: a save that Drive could not confirm, and a sync conflict. The which version do you want to keep? dialog is unchanged, and so is the phone.
site
The feedback board is now connected and taking posts. Write a feature request, a change in behavior you would like, a bug report or general feedback; no account is needed, and you can leave an email if you want to be told when there is a reply or when the request ships. Posts appear after a quick review. Until now the page said it was being connected and posting was switched off.
phone v1.23.0
Opening the phone app — or bringing it back to the foreground — used to show whatever it had last saved, and an edit made in those first seconds could end in the which version do you want to keep? question even though nothing had really diverged. The phone now reads Drive first: a slim bar says ↓ Checking Google Drive for newer changes… and taps wait until it is done, usually a second or two. If Drive cannot be reached, Skip (or a 25-second limit) lets you carry on with the saved copy, and the first save then re-reads Drive before writing. An identical copy on both sides is also no longer reported as a disagreement. The desktop is unchanged.
site
Step 4 of Getting started still said the tabs across the top are your areas, which stopped being true when the role menu ▾ replaced the per-role tabs (desktop v1.20.2). It now explains that you pick or add a role from that menu and create areas inside a role with + area. The FAQ's opening answer and the data-model labels on the engine page use the same words.
desktop v1.32.0 phone v1.22.0
The Google account whose Drive stores your FocusNexus data is now always on screen: a ☁ chip at the top of the desktop and a Data in: line under the phone's header. Click or tap it to open the account dialog, where Switch Google account shows the data stored in another account; if that account's Drive is still empty, you are asked before this device's data is copied there. Moving to a new Google account is now three guided steps on the desktop, and the last one leaves a forwarding note in the old account: a phone or browser still using it shows Your FocusNexus data moved… with a one-tap switch and stops syncing to the old account, instead of quietly carrying on there. Sign-ins in the background now also ask Google for the account this device is linked to.
site
A new part of Run it yourself, Use FocusNexus help in Claude, offers focusnexus-help.zip: a skill that lets Claude answer questions about FocusNexus from this site's pages, with links back to them. The section gives the two steps for adding it to your own Claude. The skill never sees your tasks or your Drive.
site
The engine page's design goals still described the old read-only offline mode. They now describe offline work as it has behaved since desktop v1.30.0 and phone v1.20.0: edits stay on your device while Drive is out of reach and go up on their own when the connection returns, with a prompt to choose a version if Drive changed in the meantime. The author link in the page footers now points to DeasyLab on GitHub Pages.
site
There is now a feedback board for feature requests, changes in behavior, bug reports and general feedback. No account is needed; leave an email only if you want to be told about a reply or a fix. Posts appear after a quick review, the author replies on the board, and every post has its own number and copyable link. When a request ships, its entry here will carry the post's number — like this: FB-0000 — and the post will name the release. The board link replaces the email address in the page footers.
The homepage's "A look inside" section gains a screenshot of the Eisenhower matrix, with a caption on clicking a box to open its item, the filter box, and the resize and stacking-cycle buttons.
desktop v1.31.2
The overdue side of the Eisenhower plot now stretches only as far as the most overdue item that is actually drawn. Before, an item hidden from the plot — one in the Personal role, or one removed by the filter bar — could still stretch the axis and leave empty space on the left. The axis also tightens as you filter.
desktop v1.31.1
Double-click an area's tag (the small code such as “S 12” in front of its title) to change it, the same way you rename the title; it works on team boards too. Double-clicking an area title now opens it for editing every time — before, the two clicks could roll the area up or down instead. Clicking the title or the tag no longer rolls the area; use the arrow or the empty part of the header for that.
site
The footer of every page now links to the author's website, DeasyLab, next to the copyright line.
site
The guide explained how to join a team but not how to start one. Getting started now has three steps for team owners — a dedicated Google account for the team, the Create team dialog, and sending the invite and passphrase by two different channels — and the FAQ has a matching How do I create a team and invite people?
desktop v1.31.0 phone v1.21.0
Teams have had a running log since v1.27.0; your personal tracker now keeps the same kind of record. Every change is written down as you make it — "Added task …", "Renamed … to …", "… marked DONE", "Deadline of … → …", "Deleted area …", "Focused …", and so on — with the time and the FocusNexus ID it came from. The new ☰ Log chip next to About FocusNexus opens it, newest first; on the phone the ☰ button in the header does the same, and edits made on the phone appear in the desktop's log and vice versa. The log rides your synced data, so it is in your Drive snapshots and your .json export, and it keeps the last 300 changes. Imports, reverts and conflict decisions are noted too.
desktop v1.30.1 phone v1.20.1
A first visit no longer opens on the author's own roles. A new tracker starts with just Personal and Other, and a short note explains how to begin: add a role (the hat you are wearing) from the role picker, then an area inside it — or connect Google Drive, or import a .json backup, if you already have data. The note disappears on its own once an area exists; existing users see no change. The browser tab now reads just "FocusNexus" with the version, and the last institution-specific wording has left the app. On the phone, the Tasks view opens on your first role.
desktop v1.30.0 phone v1.20.0
If Drive can't be reached, the app now keeps going instead of going read-only: an amber bar says Offline — your changes are saved on this device, edits are kept in your browser, and the app retries on its own (every 20 seconds at first, then less often, and whenever you return to the tab). Opening the app with no connection now opens editable on any device that has synced before. When the connection returns, your changes go up to Drive automatically if nothing else changed meanwhile.
Behind this is a small but important change in how the two copies are compared. Each device now remembers the last state it confirmed on Drive, so the app can tell the difference between "Drive is untouched since we last agreed" (push, silently) and "someone else changed Drive too" — the only case where an edit could be lost. In that case the app asks, showing when the two last agreed, when this device was last edited and when Drive was last changed, and you choose which version to keep; the desktop can download this device's version as a .json file first. Every Drive request also has a 20-second deadline now, so a half-dead network can't hang a save. No change to your data. The FAQ has a matching Can I work offline? entry.
desktop v1.29.1
If you open a copy of the app that was saved to disk with "Save page as", Google sign-in cannot work — the page has no web origin — and until now the read-only banner simply offered a button that did nothing. The app now recognises that situation and says what is going on, with links to the hosted app and to the new Run it yourself guide. On the hosted page and through the launcher nothing changes. Phone stays v1.19.12.
site
New homepage section Run it yourself with a bundle (both apps, the local server, Windows and Mac launchers, icons, license) built automatically from the same files as the live site; three steps to run FocusNexus from your own computer against your own Drive; and a walkthrough for hosting or modifying a copy on your own site, including the Google OAuth client such a copy needs and how to move your data across once. Two FAQ entries to match, and the top navigation now wraps on phones.
site
A look inside gains a capture of one area holding a goal, a project under it and a task under that — the three levels on one screen, sample data — and the Projected workload chart in Layers view: the author's real commitments as of today, one band per time-estimated task, stacked to a 120-day horizon. The opening line now also says it plainly: keep track of your total future time commitment. No app change; desktop stays v1.29.0, phone v1.19.12.
site
The homepage lede now says what the feature cards already did: you can create a team, so a lab or group edits shared lists together while personal lists stay private. And a new FAQ entry under The basics — What are the advantages of FocusNexus? — explains the three axes (roles, sections and hashtags), why goals are a first-class item above projects and tasks, and the shape of the underlying data model. On the engine page, "How it was built" now opens with the author's own account of the project's origin and working method. No app change; desktop stays v1.29.0, phone v1.19.12.
desktop v1.29.0 phone v1.19.12
/stale searchEvery item used to carry a hidden started / not started marker left over from the old Kanban board — it never changed after an item was created and had nothing to do with whether the item was finished. It is gone from every item, on desktop and phone alike, and drops out of your synced file and your JSON export on the next save; nothing you see changes, and Done state is untouched (it lives in the status list, as it always has).
New in the search bar: /stale 30d lists the open items you have not touched in 30 days (any number, d or w; plain /stale means 30 days), so a sweep for forgotten work is one query — it combines with words and @ filters like everything else. And a note on hashtags: #Himangi and #himangi already found the same items, on desktop and phone; that is now written down and tested so it stays that way.
desktop v1.28.0
The Tools row now saves your complete tracker as a JSON file — every area, item, badge (deadline, link, when, note, time, recurrence), focus star, time block, focus session, setting and your identity — and restores it exactly on import, with every item keeping its id. The old Markdown export/import is gone: it only ever captured the tables, turned goals back into tasks, flattened nesting and renumbered items, so an export could not be reloaded faithfully. Importing replaces the current state on this device and, on the next sync, on every device; the previous state remains in your Drive day-files (Revert). A Drive day-file itself can also be imported.
desktop v1.27.1
The +recurs badge now appears on goals, projects, tasks and sub-tasks alike — in your own areas and on team boards. Projects were the one type that could not repeat before. Anything that is due shows up in the Daily Digest's ⟳ Recurring items block (renamed from "Recurring tasks") until you mark it reviewed. Phone stays v1.19.11.
desktop v1.27.0
Every team now keeps a running log: each change records who (the member's userID), when, and what — "Renamed X to Y", "Deadline of Z set", "Deleted area W" — for every kind of edit. Open it with the new ☰ Team Log chip in the team header; it reads newest-first and works even offline or before you've unlocked the team. The log lives inside the team's own files and syncs like everything else.
Team files are also backed up the way your personal data is: each member's file gets a daily snapshot in the team's Drive folder, with the 30 most recent kept. Phone stays v1.19.11.
desktop v1.26.1
The remaining differences are gone: team items get the same up/down reorder arrows, areas can be renamed by double-click, moved, collapsed, and deleted (with a confirmation — it applies to the whole team), and area headers show the same critical / overdue counts. New ✉ invite chip in the team header: copy the team's invite string any time to bring in a new member — no need to have saved it at creation. Phone stays v1.19.11.
desktop v1.26.0
Team membership used to live only in each browser, so two computers could show different Teams tabs. It now travels with your synced data: join or create a team on one machine and it appears on your others (locked until you enter the team passphrase there once — passphrases and unlocked credentials never sync, only the encrypted invite material). Leaving a team now removes it from all your devices; the team's shared data on Drive is untouched, and re-joining with the invite brings it back everywhere. Phone stays v1.19.11.
site
The homepage now shows the app: the Daily Digest under the headline, a new A look inside section (time-blocking board, item cards, focus sessions and Tools, Status) and a picture of the Settings strip in the getting-started guide. This change log page was added and linked from the footer. No app changes — desktop stays v1.25.0, phone v1.19.11.
desktop v1.25.0 phone v1.19.11
FocusNexus goes public: the desktop page, the phone version, this website with its getting-started guide and FAQ, the engine page describing how it works, and the privacy policy. Released under CC BY-NC-SA 4.0.
The desktop app at this point includes the Daily Digest, Eisenhower matrix, time-blocking board, Projected workload chart, goals above projects, focus sessions, Markdown export/import, a Settings menu, and Teams (beta) with shared task lists, assignments, and credential rotation.