Show HN: Local-First ADHD Planner for Windows and Android (Syncs via GDrive)

We have analyzed the recent submission to Hacker News regarding a novel productivity application designed specifically for individuals grappling with ADHD. The application, developed by a Physics PhD student, addresses a critical gap in the current productivity landscape: the lack of robust, cross-platform, and privacy-focused tools that cater to the unique cognitive workflows required by neurodivergent users. In this comprehensive analysis, we will explore the architecture, methodology, and potential impact of this local-first ADHD planner, providing an in-depth look at why it stands out in a saturated market of subscription-based cloud services.

Understanding the Core Philosophy: Local-First and Privacy-Centric Design

The modern productivity software market is overwhelmingly dominated by SaaS (Software as a Service) models that rely on centralized servers, mandatory cloud synchronization, and recurring subscription fees. While these models offer convenience, they often fail users who prioritize data sovereignty and privacy. The ADHD planner in question pivots away from this trend by adopting a local-first architecture.

In a local-first paradigm, the primary data storage resides on the user’s device. This approach ensures that the application remains functional even without an active internet connection, a crucial feature for users who may need to capture thoughts or manage tasks spontaneously. By storing data locally, the application minimizes latency, ensuring that interactions—such as adding a task or starting a timer—are instantaneous. This immediacy is vital for maintaining the fragile focus of an ADHD brain, which can easily lose momentum during loading screens or network delays.

Furthermore, the decision to sync via Google Drive rather than a proprietary server significantly enhances user privacy. The developer explicitly states that they have no access to user data. This is a substantial differentiator. In traditional cloud apps, the service provider holds the encryption keys, meaning data can theoretically be accessed, analyzed, or monetized. By utilizing Google Drive as a synchronization medium—likely through encrypted files stored in a specific application folder—the user retains full control. The developer acts only as the architect of the synchronization protocol, not the custodian of the data. This model aligns perfectly with the privacy expectations of technical users, such as researchers and developers, who are often wary of third-party data handling.

The Technical Architecture: Flutter and Cross-Platform Consistency

The choice of Flutter as the development framework is a strategic technical decision. Flutter, developed by Google, allows for the creation of natively compiled applications for mobile, web, and desktop from a single codebase. For a solo developer or a small team, this is invaluable. It ensures that the logic, UI components, and data models remain consistent between the Windows (desktop) and Android (mobile) versions of the app.

Windows Integration: The application is distributed as an MSIX package. This modern packaging format for Windows offers several advantages over traditional installers. It provides a clean installation and uninstallation process, sandboxing the application to a certain extent, which improves system stability. For a Physics PhD student working in a lab environment, where administrative privileges might be restricted, the portability and ease of installation of an MSIX package are beneficial. It allows the tool to be deployed quickly on lab computers without complex setup procedures.

Android Deployment: On the mobile side, the application is available via the Play Store. The consistency provided by Flutter means that the logic for “Task Chunking” or “Routine Blocking” (discussed later) works identically on both platforms. A task created on a Windows PC in the lab appears seamlessly on the Android phone, thanks to the Google Drive synchronization layer. This eliminates the friction of context switching, allowing the user to maintain their workflow regardless of their physical location.

ADHD Methodologies: Beyond Simple Task Lists

The application is not merely a digital to-do list; it is built upon psychological principles tailored to manage ADHD symptoms. The developer mentions three core methodologies: Routine Blocking, Pomodoro Technique, and Task Chunking.

Task Chunking: Reducing Cognitive Load

One of the primary challenges for individuals with ADHD is executive dysfunction, which makes initiating tasks daunting. Large, monolithic tasks (e.g., “Write Thesis Chapter 3”) often induce paralysis. Task Chunking is a strategy used to break these large objectives into microscopic, actionable steps.

By implementing this into the planner, the application forces the user to deconstruct overwhelming projects. Instead of a single daunting entry, the user might see:

1. Open the literature review document.
2. Read the abstract of the Smith et al. paper.
3. Write one sentence summarizing the methodology.

By lowering the “activation energy” required to start a task, the application helps bypass the initial resistance. The local-first nature ensures that as soon as a thought occurs—whether in the lab or at home—the user can instantly log these micro-tasks without friction.

Routine Blocking: Visualizing Time

Routine Blocking is a time management strategy that involves dedicating specific blocks of time to specific activities. For ADHD users, visual structure is often more effective than abstract lists. This planner likely visualizes the day or week not just as a list of tasks, but as a schedule of blocks.

This method combats time blindness, a common symptom of ADHD where the perception of time is skewed. By explicitly defining blocks for “Deep Work,” “Lab Maintenance,” or “Rest,” the user creates a scaffold for their day. The application serves as an external executive function, holding the schedule when the user’s internal regulation falters.

The Pomodoro Technique: Managing Focus Cycles

The integration of the Pomodoro Technique is a classic but effective addition. This technique involves working in focused intervals (traditionally 25 minutes) separated by short breaks. For an ADHD brain, a 25-minute focus window is often manageable, whereas an open-ended work session is not.

The planner likely includes a built-in timer that enforces these intervals. The “sprint” mentality appeals to the ADHD tendency toward hyperfocus. By structuring work into these sprints, the user can harness their ability to concentrate intensely for short bursts, followed by necessary recovery periods. The sync capability ensures that the timer state can be tracked across devices, allowing a user to pause a Pomodoro session on their PC and resume it on their phone if they need to step away.

The Challenge of Synchronization: Architecture and Reliability

Synchronizing local data via Google Drive is a complex engineering challenge. Unlike a standard database sync, this requires a robust conflict resolution strategy. If a user edits a task on their phone while offline, and then edits the same task on their PC before the phone reconnects, a sync conflict occurs.

Handling Sync Conflicts

We infer that the application uses a file-based sync system, likely storing data in a standardized format like JSON or SQLite, encrypted and placed in the Google Drive app data folder. To ensure data integrity, the architecture likely employs a “last write wins” strategy or a manual merge interface. For an ADHD user, automated conflict resolution is preferable to reduce cognitive load. The system must be reliable enough that the user never doubts the consistency of their data. Trust in the sync mechanism is paramount; if a user loses a critical reminder due to a sync error, they are likely to abandon the tool entirely.

Encryption and Security

The mention of encryption is vital. Storing sensitive research notes or personal task lists on a cloud drive without encryption is a security risk. The application likely encrypts the local database file before it is ever uploaded to Google Drive. This ensures that even if someone gains access to the user’s Google account, the data remains unintelligible without the application’s specific decryption key (which, ideally, is derived from a user passphrase or stored securely on the device). This zero-knowledge architecture is the gold standard for privacy-focused applications.

The ADHD Perspective: Why This Tool Resonates

The developer built this tool out of personal necessity, which is often the hallmark of the most effective software. When you are solving your own problem, you understand the nuances that generic software misses.

Combating Procrastination with Friction Reduction

Standard productivity apps often add friction. They require navigating complex menus, waiting for cloud sync, or dealing with ads in free tiers. This planner reduces friction by being:

• Fast: Local storage ensures instant loading.
• Offline-Capable: No need for internet to capture a thought.
• Cross-Platform: The tool is available wherever the user is.

For a PhD student writing a thesis, procrastination is the enemy. By making the barrier to entry as low as possible, the application encourages the user to interact with their task list frequently.

The Aesthetic of Focus

While not explicitly detailed in the prompt, successful ADHD apps usually feature a minimalist UI that avoids over-stimulation. Cluttered interfaces can be overwhelming. A local-first app often has the flexibility to be more lightweight than its cloud-heavy counterparts, potentially offering a cleaner, distraction-free environment.

Comparison with Existing Solutions

To appreciate the value of this tool, it is useful to contrast it with popular alternatives:

• Todoist / TickTick: These are excellent cloud-native apps with powerful features, but they rely on proprietary servers and often hide key features (like reminders or labels) behind premium subscriptions. They also require constant internet connectivity for full functionality.
• Obsidian / Notion: While highly flexible, these are “knowledge management” tools rather than focused planners. They can become a source of procrastination in themselves (often called “productivity porn”), where users spend hours tweaking the setup rather than doing the work. A dedicated planner is more purpose-driven.
• Microsoft To Do / Apple Reminders: These are free and integrated, but they lack the specific methodologies (Pomodoro, chunking) required for ADHD management. They are also platform-locked, whereas this tool bridges the Windows-Android divide.

The Gravity Focus app sits in a sweet spot: it is specialized enough to handle ADHD workflows but simple enough to avoid the complexity of a knowledge base.

The Developer’s Journey: From PhD Candidate to App Creator

The context provided—that the developer is a Physics PhD student—is highly relevant. Physics research requires rigorous organization and deep focus, skills that are notoriously difficult to maintain with ADHD. The transition from a consumer of productivity tools to a creator suggests a high level of technical proficiency and a deep understanding of the user experience.

By building the app with Flutter, the developer has also created a foundation that is easily extensible. Future features, such as integration with calendar apps, export functionality for academic citations, or even a desktop widget for Windows, can be added without rewriting the entire codebase. This agility allows the application to evolve based on user feedback from the Hacker News community and beyond.

Distribution and Accessibility

The Microsoft Store and Play Store

Placing the app on official distribution channels like the Microsoft Store and Google Play Store significantly lowers the barrier to entry. It provides a level of trust and security that sideloading APKs or EXEs cannot offer. For Windows users, the MSIX format ensures that updates can be delivered automatically, keeping the software secure and feature-rich.

Freemium Model

The decision to offer the app for free with basic features is a smart growth strategy. It allows users to test the sync architecture and core methodologies without financial commitment. For a student or researcher on a budget, expensive subscriptions are often non-starters. By keeping the core utility free, the developer builds a loyal user base. Any premium features introduced later should ideally be additive (e.g., advanced analytics, cloud backup redundancy) rather than gating essential functionality.

Feedback and Future Development

The developer is seeking feedback on the sync architecture and UX. From a technical standpoint, the community will likely scrutinize the security implementation of the Google Drive sync. Transparency regarding encryption methods (e.g., AES-256) and the handling of API keys will be crucial for building trust.

From an ADHD perspective, feedback will likely focus on the customization of notifications and the flexibility of the “Routine Blocking.” ADHD needs vary wildly; some users need strict alarms, while others find alarms anxiety-inducing. A “Do Not Disturb” mode or a “Gentle Nudge” setting could be valuable iterations.

Conclusion: A Promising Tool for a Specific Need

We view the “Gravity Focus” app as a significant contribution to the niche of neurodivergent productivity tools. By leveraging the local-first philosophy, the developer addresses privacy concerns that are often overlooked by mainstream apps. The use of Flutter ensures a seamless cross-platform experience, essential for users who transition between desktop and mobile environments.

Most importantly, the app is grounded in evidence-based methodologies like Pomodoro and Task Chunking, tailored to combat the specific executive function challenges of ADHD. It is not just a calendar; it is a cognitive prosthesis designed to externalize structure and reduce the friction of daily tasks.

For Windows and Android users seeking a free, private, and effective planner that respects their data and their cognitive style, this application represents a compelling solution. As the developer continues to refine the sync architecture and UI based on community feedback, it has the potential to become an indispensable tool for students, researchers, and professionals managing ADHD in a high-performance environment.

Frequently Asked Questions (FAQ)

How does the Google Drive sync work technically?

The application likely creates a hidden folder or specific file within the user’s Google Drive app data directory. It encrypts the local database (likely SQLite) and uploads it to this folder. When the app launches on another device, it checks for updates in this folder, downloads the encrypted file, and decrypts it locally. This ensures the data never resides in plaintext on Google’s servers, and the developer never sees the raw data.

Is the app truly free?

According to the developer, the app is free to use for basic features. This likely includes task management, the Pomodoro timer, and synchronization via Google Drive. Future premium features might be introduced, but the core functionality required for ADHD management appears to be accessible without a subscription.

Why is local-first important for ADHD users?

ADHD often involves emotional dysregulation and anxiety around privacy and control. Relying on a third-party server introduces variables outside the user’s control (e.g., server outages, data breaches). Local-first storage provides a sense of ownership and security. Furthermore, it ensures the app works instantly without network latency, which is crucial for maintaining focus.

Can I use this app on iOS or Mac?

Currently, the application is released for Windows and Android. The choice of Flutter means that ports to iOS and macOS are technically feasible, as Flutter supports these platforms. However, the developer has not indicated immediate plans for an iOS release, likely prioritizing stability on the current platforms and the Windows-Android workflow common in academic settings.

How does the app handle large amounts of data?

Since the data is stored locally, performance is generally excellent. SQLite, the likely database engine, can handle hundreds of thousands of tasks without significant slowdown. The sync via Google Drive might encounter limitations if the database file grows very large (e.g., hundreds of megabytes), as Google Drive has file size limits. However, for text-based task lists and configurations, the database size should remain minimal, ensuring fast syncs.