June 1, 2024 – Version 0.3.0
What if our productivity tools actually worked together instead of competing for our attention?
That’s the question that led to S.I.R.I.U.S. (SMART, INTELLIGENT, RESPONSIVE, INTEGRATIVE, USER-FRIENDLY, SYSTEM). In a world where every app wants to be the center of our digital lives, we’re left juggling between platforms like digital acrobats, constantly switching contexts and losing focus.
The project began with a simple discovery: Siri shortcuts could accept JSON payloads. This revelation on my iPhone led to the realization that I could build a Node.js server with REST API integrations and pass commands to Siri shortcuts, enabling voice-activated task creation like building Trello boards. What started as a mobile experiment has evolved into a comprehensive privacy-first AI assistant.
Key architectural decision: Started on mobile using Replit, proving that complex development workflows can be achieved without traditional desktop environments. Today, development continues in a proper IDE while maintaining the mobile-first architecture.
Added
- Siri Shortcuts Integration: The foundational discovery that started it all. Siri shortcuts accepting JSON payloads enabled voice-activated API interactions. Create project boards, schedule meetings, or update documentation, all hands-free. This reduces cognitive load and improves accessibility.
- Node.js Backend: Built a REST API server that could integrate with various services (Trello, Notion, Google Calendar) and pass structured commands to Siri shortcuts. The server acts as a bridge between voice commands and API actions.
- TypeScript Migration: Currently working on migrating from JavaScript to TypeScript for better type safety and developer experience. This decision was driven by the complexity of managing multiple API integrations and the need for robust error handling. The trade-off? Increased build complexity and learning curve, but significantly reduced runtime errors.
- Mistral AI Integration: Replacing Ollama with Mistral AI to align with EU data sovereignty directives. This architectural decision ensures data processing remains within European jurisdiction, addressing GDPR compliance concerns. Being based in Europe, this actually provides better latency and regional alignment.
- PWA Architecture: The Progressive Web App approach emerged naturally from the mobile-first development process. Built on iPhone using Replit, the PWA architecture ensures cross-platform compatibility and offline functionality.
- Memory System: Implemented persistent local storage for user patterns and learning, including circadian rhythm analysis for personalized interactions.
Improved
- Mobile-First Development: Proved that powerful applications can be built entirely on mobile devices. Using Replit on my iPhone, I developed a full-featured integration platform that challenges traditional development norms. The PWA architecture literally emerged from the constraint of building on mobile. While current development happens in a proper IDE, the mobile-first approach remains foundational.
- Service Connectors: Built resilient connections to third-party APIs with smart retry mechanisms and error handling. Each service connector adapts when API rules change or permissions need updating. The key is always having a backup plan when the primary connection fails.
- Documentation: Created clear, mobile-friendly documentation that helps users get started quickly. Straightforward guides get you from zero to productive in minutes, optimized for mobile consumption.
- Offline Sync: Implemented robust offline-first architecture that keeps your data in sync even when you’re on the go. Data syncs automatically when connectivity is restored, maintaining productivity regardless of network conditions.
Learned
- API Negotiation: Getting API access requires persistence and clear communication. The approval process involves multiple rounds of documentation, security reviews, and compliance checks. Successfully receiving API access after months of negotiation demonstrates the importance of building relationships with platform providers.
- Mobile Development Power: Discovered that modern mobile development tools are powerful enough to build complex applications. The iPhone and Replit combination proved to be a surprisingly capable development environment, demonstrating that traditional desktop constraints can be overcome with the right tools.
- Authentication Management: Mastered the art of securely handling multiple API keys and tokens, ensuring that your data stays safe while maintaining a smooth user experience. This requires careful key rotation, secure storage practices, and proper access controls.
- PWA Implementation: Learned that building a PWA isn’t just about offline support, it’s about creating a seamless experience that works everywhere. Users can install it on their home screen and use it like a native app, but with all the benefits of the web.
Architectural Decisions and Trade-offs
Siri Shortcuts Foundation:
- Decision: Build around Siri shortcuts accepting JSON
- Rationale: Enable voice-activated API interactions without complex voice recognition
- Trade-offs:
- Limited to iOS ecosystem for voice commands
- Requires Siri shortcuts setup by users
- Provides seamless voice-to-action workflow
TypeScript Migration:
- Decision: Migrate from JavaScript to TypeScript
- Rationale: Complex API integrations require better type safety and error handling
- Trade-offs:
- Increased build complexity and learning curve
- Significantly reduced runtime errors and improved maintainability
- Better IDE support and developer experience
Mistral AI Integration:
- Decision: Replace Ollama with Mistral AI
- Rationale: EU data sovereignty compliance and GDPR alignment
- Trade-offs:
- Better latency for European users compared to US-based alternatives
- Improved regulatory compliance and data protection
- Reduced infrastructure maintenance overhead
Mobile-First Development:
- Decision: Start development on mobile using Replit, evolve to IDE
- Rationale: Challenge traditional development norms and prove mobile capability, then scale with proper tools
- Trade-offs:
- Initial development constraints led to innovative PWA architecture
- Current IDE development provides better productivity
- Maintains mobile-first design principles
PWA Architecture:
- Decision: Progressive Web App over native mobile app
- Rationale: Cross-platform compatibility and offline functionality
- Trade-offs:
- Limited access to native device features
- Improved deployment and update process
- Better web integration and SEO
Current State
Today, S.I.R.I.U.S. has evolved into a comprehensive privacy-first AI assistant with the following architecture:
- EU-Compliant AI Engine: Powered by Mistral AI for privacy-preserving operations within European jurisdiction
- Memory System: Persistent local storage for user patterns and circadian learning
- Multi-Platform Support: Web, mobile app, and browser extension interfaces
- Full API Integrations: Notion, Asana, Jira, Trello, Google Calendar, and more
- Worker Threads: Efficient handling of CPU-intensive tasks
- WebSocket Communication: Real-time updates and interactions
The project is now open source on GitHub with 2 stars and active development, demonstrating how a simple mobile discovery can evolve into a sophisticated privacy-first productivity platform.
Reflection
The most interesting part? How the quest for API access revealed the deeper problem: our tools are designed to keep us locked in, not to work together.
I initially thought building on mobile would be the biggest challenge, but it turned out that getting API permissions was the real circus act. Each service has its own rules, its own approval process, and its own way of saying “maybe.” But the deeper issue is that these platforms are designed to compete for our attention, not to collaborate for our benefit.
The real challenge wasn’t technical, it was ethical. Every “no” from an API provider was a reminder that our digital tools are built to serve corporate interests, not human needs. But sometimes, a “no” is just an opportunity to build something better.
The question isn’t whether we can integrate these tools, it’s whether we should accept tools that don’t respect our time and autonomy.
Next Steps
- Expanding to more productivity tools (Todoist, Asana)
- Enhancing calendar features
- Adding email integration
- Implementing news aggregation
- Integrating health tracking
- Adding smart home controls
- Improving offline sync capabilities