Unfinished things are allowed here. SerKal began in Google Sheets, became a standalone Windows application and then made the leap to Android. This development diary follows that journey through drafts, working builds, successes and changing ideas.
8 March 2025
Before SerKal became a program of its own
SerKal originally lived entirely in Google Sheets and Google Apps Script. Episode dates were stored in a spreadsheet, while a sidebar collected title, year, season, start date and episode count.
The starting point: series management in Google Sheets with its own entry sidebar.
Seasons and episodes already belonged together, broadcast dates were listed clearly, and the calendar stood at the centre.
This was the starting point from which SerKal Desktop β and later the Android idea β emerged.
4 August 2026
A rather big idea
What if SerKal could simply be installed? No Apps Script editor, no modules to copy and no personal web app to deploy. Download, install and start.
That question became the plan for SerKal Desktop. The existing interface and years of program logic formed the foundation.
The first design sketch: architecture, workflow and a possible appearance. A target, not the finished interface.
7 August 2026
Three days later: it is alive
SerKal Desktop 0.0.1 β Build 0001 ran as a standalone Windows application.
The first desktop application that was actually built.
No series search, archive or calendar yet. But it ran.
Electron and Node.js formed the new foundation.
β Windows windowβ Electronβ Node.jsβ interfaceβ searchβ archiveβ calendar
11 August 2026
Version 0.0.2 β the interface moves in
The familiar SerKal interface moved into the Windows application. Full-screen operation, Light and Dark Mode, and switching between German and English already worked.
German interface in Light Mode.English interface in Dark Mode.
This was the first version that not only ran, but already looked recognisably like SerKal.
August 2026
Versions 0.0.3 to 0.0.5 β real data returns
The interface study became a real desktop edition. Version 0.0.5 loaded the existing archive, displayed season information, TMDB descriptions and artwork, and allowed series to be searched, added and edited.
Google Calendar β now directly
After one OAuth approval, SerKal could write episode dates straight into the selected Google Calendar. ICS remained available for other calendars.
The first complete practical test used Reacher, season 4. Every episode date appeared automatically with the correct calendar colour.
β searchβ archiveβ TMDB detailsβ direct calendar entriesβ save and edit
All eight steps of the original desktop workflow had now been implemented.
September 2026
The workshop becomes SerKal Desktop 1.0
After many intermediate builds, release candidates and tests on several computers, SerKal Desktop 1.0 was released. Its technical version was 1.0.5, displayed as Build 1.0005.
The empty Electron window had become an installable Windows program with guided setup, TMDB search, an archive and calendar support.
β Windows installerβ German and Englishβ TMDB searchβ series archiveβ Google Calendarβ ICS alternative
In roughly a year and a half, a Google Sheet had become a standalone desktop application.
September 2026
The next beginning: SerKal on Android
A first APK launched on a Google Pixel 8 and a Samsung tablet. The prototype already switched between German and English, but the desktop interface had to be reshaped for smaller screens, safe edges and landscape use.
β first APKβ Pixel 8β Samsung tabletβ German/Englishβ scalable interfaceβ desktop feature set
The first prototype ran β the Android story had begun.
26 October 2026
SerKal 1.2: Android becomes public
SerKal 1.2 was released for Windows and Android. Both editions could share the same archive; changes were saved safely on the device and then synchronised with Google in the background.
Search became smarter, maintenance gained a result list, announced seasons could remain without invented episode dates, streaming providers could be shown by country, and users could choose the authoritative archive when copies disagreed.
Android grows up
The Android interface used available space more effectively. Its compact footer included language, Light/Dark, calendar, help and a genuine Exit action.
β Desktop 1.2β public Android APKβ shared archiveβ Windows and Androidβ Light and Dark Modeβ verified signatures
The cautious September prototype became part of one shared public SerKal release.
From 1.2.0 to Desktop 1.2.6: Calendar work that can handle large jobs
The first public 1.2 release completed the major platform transition. Everyday use then showed where the next workshop effort was needed: not new buttons, but resilient Calendar processing and a clearer Google sign-in experience.
Versions 1.2.1 through 1.2.4 learned to touch only affected series and seasons, avoid rewriting completed scopes and distinguish archive storage from unfinished Calendar work. Small edits therefore stopped causing hundreds of unnecessary Google operations. Logs became more precise without exposing private Calendar content.
Desktop 1.2.5: Room for large Calendar runs
Large updates now pause after every 20 successful writes. Temporary Google limits trigger longer retries with a visible countdown, and Calendar work has its own time allowance instead of failing at the former general 45-second boundary. Completed work is retained; a later attempt continues with the remaining tasks.
Desktop 1.2.6: A separate window for Google
Sign-in now opens in a separate, normally sized external browser window without reshaping an existing browser window. When it finishes, SerKal returns and reports the real archive count. The practical acceptance run correctly showed 92 entries instead of the former βundefined entriesβ message.
β Desktop 1.2.6 releasedβ Android 1.2.4 remains compatibleβ archive revision 38β more resilient large Calendar runsβ separate Google windowβ real archive count
Windows 1.2.6 is now public. Android deliberately remains at 1.2.4 β a shared archive, but currently not the same product version.
Still remembered: The Google window may cover the smaller SerKal message; moving it briefly aside is enough when needed. A better window arrangement, a permanently visible genuine Google status and the known βAdd calendarβ browser detour remain for a later Desktop release.
SerKal has grown from a Windows sketch into a program for several devices. New workshop reports will follow when the next solid milestone has genuinely been reached.