refactor: centralize platform-specific behavior in platform services

- Add platform-specific capability methods to PlatformService interface:
  - getExportInstructions()
  - getExportSuccessMessage()
  - needsSecondaryDownloadLink()
  - needsDownloadCleanup()

- Update platform service implementations:
  - WebPlatformService: Implement web-specific export behavior
  - CapacitorPlatformService: Implement mobile-specific export behavior
  - ElectronPlatformService: Add placeholder for export functionality
  - PyWebViewPlatformService: Add placeholder for export functionality

- Refactor DataExportSection component:
  - Remove direct platform checks (isWeb, isCapacitor, etc.)
  - Use platform service capabilities for UI behavior
  - Improve error handling and logging
  - Add proper cleanup for web platform downloads

- Update PlatformServiceFactory:
  - Make getInstance() async to support dynamic imports
  - Improve platform service initialization

- Fix code style and documentation:
  - Update JSDoc comments
  - Fix string quotes consistency
  - Add proper error handling
  - Improve logging messages

- Update Vite config:
  - Add all Capacitor dependencies to external list
  - Ensure consistent handling across platforms

.cursor/rules/absurd-sql.mdc

@@ -1,153 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: true
----
-# Absurd SQL - Cursor Development Guide
-
-## Project Overview
-Absurd SQL is a backend implementation for sql.js that enables persistent SQLite databases in the browser by using IndexedDB as a block storage system. This guide provides rules and best practices for developing with this project in Cursor.
-
-## Project Structure
-```
-absurd-sql/
-├── src/               # Source code
-├── dist/             # Built files
-├── package.json      # Dependencies and scripts
-├── rollup.config.js  # Build configuration
-└── jest.config.js    # Test configuration
-```
-
-## Development Rules
-
-### 1. Worker Thread Requirements
-- All SQL operations MUST be performed in a worker thread
-- Main thread should only handle worker initialization and communication
-- Never block the main thread with database operations
-
-### 2. Code Organization
-- Keep worker code in separate files (e.g., `*.worker.js`)
-- Use ES modules for imports/exports
-- Follow the project's existing module structure
-
-### 3. Required Headers
-When developing locally or deploying, ensure these headers are set:
-```
-Cross-Origin-Opener-Policy: same-origin
-Cross-Origin-Embedder-Policy: require-corp
-```
-
-### 4. Browser Compatibility
-- Primary target: Modern browsers with SharedArrayBuffer support
-- Fallback mode: Safari (with limitations)
-- Always test in both modes
-
-### 5. Database Configuration
-Recommended database settings:
-```sql
-PRAGMA journal_mode=MEMORY;
-PRAGMA page_size=8192;  -- Optional, but recommended
-```
-
-### 6. Development Workflow
-1. Install dependencies:
-   ```bash
-   yarn add @jlongster/sql.js absurd-sql
-   ```
-
-2. Development commands:
-   - `yarn build` - Build the project
-   - `yarn jest` - Run tests
-   - `yarn serve` - Start development server
-
-### 7. Testing Guidelines
-- Write tests for both SharedArrayBuffer and fallback modes
-- Use Jest for testing
-- Include performance benchmarks for critical operations
-
-### 8. Performance Considerations
-- Use bulk operations when possible
-- Monitor read/write performance
-- Consider using transactions for multiple operations
-- Avoid unnecessary database connections
-
-### 9. Error Handling
-- Implement proper error handling for:
-  - Worker initialization failures
-  - Database connection issues
-  - Concurrent access conflicts (in fallback mode)
-  - Storage quota exceeded scenarios
-
-### 10. Security Best Practices
-- Never expose database operations directly to the client
-- Validate all SQL queries
-- Implement proper access controls
-- Handle sensitive data appropriately
-
-### 11. Code Style
-- Follow ESLint configuration
-- Use async/await for asynchronous operations
-- Document complex database operations
-- Include comments for non-obvious optimizations
-
-### 12. Debugging
-- Use `jest-debug` for debugging tests
-- Monitor IndexedDB usage in browser dev tools
-- Check worker communication in console
-- Use performance monitoring tools
-
-## Common Patterns
-
-### Worker Initialization
-```javascript
-// Main thread
-import { initBackend } from 'absurd-sql/dist/indexeddb-main-thread';
-
-function init() {
-  let worker = new Worker(new URL('./index.worker.js', import.meta.url));
-  initBackend(worker);
-}
-```
-
-### Database Setup
-```javascript
-// Worker thread
-import initSqlJs from '@jlongster/sql.js';
-import { SQLiteFS } from 'absurd-sql';
-import IndexedDBBackend from 'absurd-sql/dist/indexeddb-backend';
-
-async function setupDatabase() {
-  let SQL = await initSqlJs({ locateFile: file => file });
-  let sqlFS = new SQLiteFS(SQL.FS, new IndexedDBBackend());
-  SQL.register_for_idb(sqlFS);
-  
-  SQL.FS.mkdir('/sql');
-  SQL.FS.mount(sqlFS, {}, '/sql');
-  
-  return new SQL.Database('/sql/db.sqlite', { filename: true });
-}
-```
-
-## Troubleshooting
-
-### Common Issues
-1. SharedArrayBuffer not available
-   - Check COOP/COEP headers
-   - Verify browser support
-   - Test fallback mode
-
-2. Worker initialization failures
-   - Check file paths
-   - Verify module imports
-   - Check browser console for errors
-
-3. Performance issues
-   - Monitor IndexedDB usage
-   - Check for unnecessary operations
-   - Verify transaction usage
-
-## Resources
-- [Project Demo](https://priceless-keller-d097e5.netlify.app/)
-- [Example Project](https://github.com/jlongster/absurd-example-project)
-- [Blog Post](https://jlongster.com/future-sql-web)
-- [SQL.js Documentation](https://github.com/sql-js/sql.js/) 

.cursor/rules/architectural_decision_record.mdc

@@ -1,292 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: true
----
-# TimeSafari Cross-Platform Architecture Guide
-
-## 1. Platform Support Matrix
-
-| Feature | Web (PWA) | Capacitor (Mobile) | Electron (Desktop) | PyWebView (Desktop) |
-|---------|-----------|-------------------|-------------------|-------------------|
-| QR Code Scanning | WebInlineQRScanner | @capacitor-mlkit/barcode-scanning | Not Implemented | Not Implemented |
-| Deep Linking | URL Parameters | App URL Open Events | Not Implemented | Not Implemented |
-| File System | Limited (Browser API) | Capacitor Filesystem | Electron fs | PyWebView Python Bridge |
-| Camera Access | MediaDevices API | Capacitor Camera | Not Implemented | Not Implemented |
-| Platform Detection | Web APIs | Capacitor.isNativePlatform() | process.env checks | process.env checks |
-
-## 2. Project Structure
-
-### 2.1 Core Directories
-```
-src/
-├── components/     # Vue components
-├── services/       # Platform services and business logic
-├── views/         # Page components
-├── router/        # Vue router configuration
-├── types/         # TypeScript type definitions
-├── utils/         # Utility functions
-├── lib/           # Core libraries
-├── platforms/     # Platform-specific implementations
-├── electron/      # Electron-specific code
-├── constants/     # Application constants
-├── db/           # Database related code
-├── interfaces/    # TypeScript interfaces and type definitions
-└── assets/        # Static assets
-```
-
-### 2.2 Entry Points
-```
-src/
-├── main.ts              # Base entry
-├── main.common.ts       # Shared initialization
-├── main.capacitor.ts    # Mobile entry
-├── main.electron.ts     # Electron entry
-├── main.pywebview.ts    # PyWebView entry
-└── main.web.ts          # Web/PWA entry
-```
-
-### 2.3 Build Configurations
-```
-root/
-├── vite.config.common.mts    # Shared config
-├── vite.config.capacitor.mts # Mobile build
-├── vite.config.electron.mts  # Electron build
-├── vite.config.pywebview.mts # PyWebView build
-├── vite.config.web.mts      # Web/PWA build
-└── vite.config.utils.mts    # Build utilities
-```
-
-## 3. Service Architecture
-
-### 3.1 Service Organization
-```
-services/
-├── QRScanner/           # QR code scanning service
-│   ├── WebInlineQRScanner.ts
-│   └── interfaces.ts
-├── platforms/          # Platform-specific services
-│   ├── WebPlatformService.ts
-│   ├── CapacitorPlatformService.ts
-│   ├── ElectronPlatformService.ts
-│   └── PyWebViewPlatformService.ts
-└── factory/           # Service factories
-    └── PlatformServiceFactory.ts
-```
-
-### 3.2 Service Factory Pattern
-```typescript
-// PlatformServiceFactory.ts
-export class PlatformServiceFactory {
-  private static instance: PlatformService | null = null;
-
-  public static getInstance(): PlatformService {
-    if (!PlatformServiceFactory.instance) {
-      const platform = process.env.VITE_PLATFORM || "web";
-      PlatformServiceFactory.instance = createPlatformService(platform);
-    }
-    return PlatformServiceFactory.instance;
-  }
-}
-```
-
-## 4. Feature Implementation Guidelines
-
-### 4.1 QR Code Scanning
-
-1. **Service Interface**
-```typescript
-interface QRScannerService {
-  checkPermissions(): Promise<boolean>;
-  requestPermissions(): Promise<boolean>;
-  isSupported(): Promise<boolean>;
-  startScan(): Promise<void>;
-  stopScan(): Promise<void>;
-  addListener(listener: ScanListener): void;
-  onStream(callback: (stream: MediaStream | null) => void): void;
-  cleanup(): Promise<void>;
-}
-```
-
-2. **Platform-Specific Implementation**
-```typescript
-// WebInlineQRScanner.ts
-export class WebInlineQRScanner implements QRScannerService {
-  private scanListener: ScanListener | null = null;
-  private isScanning = false;
-  private stream: MediaStream | null = null;
-  private events = new EventEmitter();
-
-  // Implementation of interface methods
-}
-```
-
-### 4.2 Deep Linking
-
-1. **URL Structure**
-```typescript
-// Format: timesafari://<route>[/<param>][?queryParam1=value1]
-interface DeepLinkParams {
-  route: string;
-  params?: Record<string, string>;
-  query?: Record<string, string>;
-}
-```
-
-2. **Platform Handlers**
-```typescript
-// Capacitor
-App.addListener("appUrlOpen", handleDeepLink);
-
-// Web
-router.beforeEach((to, from, next) => {
-  handleWebDeepLink(to.query);
-});
-```
-
-## 5. Build Process
-
-### 5.1 Environment Configuration
-```typescript
-// vite.config.common.mts
-export function createBuildConfig(mode: string) {
-  return {
-    define: {
-      'process.env.VITE_PLATFORM': JSON.stringify(mode),
-      'process.env.VITE_PWA_ENABLED': JSON.stringify(!isNative),
-      __IS_MOBILE__: JSON.stringify(isCapacitor),
-      __USE_QR_READER__: JSON.stringify(!isCapacitor)
-    }
-  };
-}
-```
-
-### 5.2 Platform-Specific Builds
-
-```bash
-# Build commands from package.json
-"build:web": "vite build --config vite.config.web.mts",
-"build:capacitor": "vite build --config vite.config.capacitor.mts",
-"build:electron": "vite build --config vite.config.electron.mts",
-"build:pywebview": "vite build --config vite.config.pywebview.mts"
-```
-
-## 6. Testing Strategy
-
-### 6.1 Test Configuration
-```typescript
-// playwright.config-local.ts
-const config: PlaywrightTestConfig = {
-  projects: [
-    {
-      name: 'web',
-      use: { browserName: 'chromium' }
-    },
-    {
-      name: 'mobile',
-      use: { ...devices['Pixel 5'] }
-    }
-  ]
-};
-```
-
-### 6.2 Platform-Specific Tests
-```typescript
-test('QR scanning works on mobile', async ({ page }) => {
-  test.skip(!process.env.MOBILE_TEST, 'Mobile-only test');
-  // Test implementation
-});
-```
-
-## 7. Error Handling
-
-### 7.1 Global Error Handler
-```typescript
-function setupGlobalErrorHandler(app: VueApp) {
-  app.config.errorHandler = (err, instance, info) => {
-    logger.error("[App Error]", {
-      error: err,
-      info,
-      component: instance?.$options.name
-    });
-  };
-}
-```
-
-### 7.2 Platform-Specific Error Handling
-```typescript
-// API error handling for Capacitor
-if (process.env.VITE_PLATFORM === 'capacitor') {
-  logger.error(`[Capacitor API Error] ${endpoint}:`, {
-    message: error.message,
-    status: error.response?.status
-  });
-}
-```
-
-## 8. Best Practices
-
-### 8.1 Code Organization
-- Use platform-specific directories for unique implementations
-- Share common code through service interfaces
-- Implement feature detection before using platform capabilities
-- Keep platform-specific code isolated in dedicated directories
-- Use TypeScript interfaces for cross-platform compatibility
-
-### 8.2 Platform Detection
-```typescript
-const platformService = PlatformServiceFactory.getInstance();
-const capabilities = platformService.getCapabilities();
-
-if (capabilities.hasCamera) {
-  // Implement camera features
-}
-```
-
-### 8.3 Feature Implementation
-1. Define platform-agnostic interface
-2. Create platform-specific implementations
-3. Use factory pattern for instantiation
-4. Implement graceful fallbacks
-5. Add comprehensive error handling
-6. Use dependency injection for better testability
-
-## 9. Dependency Management
-
-### 9.1 Platform-Specific Dependencies
-```json
-{
-  "dependencies": {
-    "@capacitor/core": "^6.2.0",
-    "electron": "^33.2.1",
-    "vue": "^3.4.0"
-  }
-}
-```
-
-### 9.2 Conditional Loading
-```typescript
-if (process.env.VITE_PLATFORM === 'capacitor') {
-  await import('@capacitor/core');
-}
-```
-
-## 10. Security Considerations
-
-### 10.1 Permission Handling
-```typescript
-async checkPermissions(): Promise<boolean> {
-  if (platformService.isCapacitor()) {
-    return await checkNativePermissions();
-  }
-  return await checkWebPermissions();
-}
-```
-
-### 10.2 Data Storage
-- Use secure storage mechanisms for sensitive data
-- Implement proper encryption for stored data
-- Follow platform-specific security guidelines
-- Regular security audits and updates
-
-This document should be updated as new features are added or platform-specific implementations change. Regular reviews ensure it remains current with the codebase.

.cursor/rules/crowd-funder-for-time-pwa/docs/camera-implementation.mdc

@@ -1,222 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: false
----
-# Camera Implementation Documentation
-
-## Overview
-
-This document describes how camera functionality is implemented across the TimeSafari application. The application uses cameras for two main purposes:
-
-1. QR Code scanning
-2. Photo capture
-
-## Components
-
-### QRScannerDialog.vue
-
-Primary component for QR code scanning in web browsers.
-
-**Key Features:**
-
-- Uses `qrcode-stream` for web-based QR scanning
-- Supports both front and back cameras
-- Provides real-time camera status feedback
-- Implements error handling with user-friendly messages
-- Includes camera switching functionality
-
-**Camera Access Flow:**
-
-1. Checks for camera API availability
-2. Enumerates available video devices
-3. Requests camera permissions
-4. Initializes camera stream with preferred settings
-5. Handles various error conditions with specific messages
-
-### PhotoDialog.vue
-
-Component for photo capture and selection.
-
-**Key Features:**
-
-- Cross-platform photo capture interface
-- Image cropping capabilities
-- File selection fallback
-- Unified interface for different platforms
-
-## Services
-
-### QRScanner Services
-
-#### WebDialogQRScanner
-
-Web-based implementation of QR scanning.
-
-**Key Methods:**
-
-- `checkPermissions()`: Verifies camera permission status
-- `requestPermissions()`: Requests camera access
-- `isSupported()`: Checks for camera API support
-- Handles various error conditions with specific messages
-
-#### CapacitorQRScanner
-
-Native implementation using Capacitor's MLKit.
-
-**Key Features:**
-
-- Uses `@capacitor-mlkit/barcode-scanning`
-- Supports both front and back cameras
-- Implements permission management
-- Provides continuous scanning capability
-
-### Platform Services
-
-#### WebPlatformService
-
-Web-specific implementation of platform features.
-
-**Camera Capabilities:**
-
-- Uses HTML5 file input with capture attribute
-- Falls back to file selection if camera unavailable
-- Processes captured images for consistent format
-
-#### CapacitorPlatformService
-
-Native implementation using Capacitor.
-
-**Camera Features:**
-
-- Uses `Camera.getPhoto()` for native camera access
-- Supports image editing
-- Configures high-quality image capture
-- Handles base64 image processing
-
-#### ElectronPlatformService
-
-Desktop implementation (currently unimplemented).
-
-**Status:**
-
-- Camera functionality not yet implemented
-- Planned to use Electron's media APIs
-
-## Platform-Specific Considerations
-
-### iOS
-
-- Requires `NSCameraUsageDescription` in Info.plist
-- Supports both front and back cameras
-- Implements proper permission handling
-
-### Android
-
-- Requires camera permissions in manifest
-- Supports both front and back cameras
-- Handles permission requests through Capacitor
-
-### Web
-
-- Requires HTTPS for camera access
-- Implements fallback mechanisms
-- Handles browser compatibility issues
-
-## Error Handling
-
-### Common Error Scenarios
-
-1. No camera found
-2. Permission denied
-3. Camera in use by another application
-4. HTTPS required
-5. Browser compatibility issues
-
-### Error Response
-
-- User-friendly error messages
-- Troubleshooting tips
-- Clear instructions for resolution
-- Platform-specific guidance
-
-## Security Considerations
-
-### Permission Management
-
-- Explicit permission requests
-- Permission state tracking
-- Graceful handling of denied permissions
-
-### Data Handling
-
-- Secure image processing
-- Proper cleanup of camera resources
-- No persistent storage of camera data
-
-## Best Practices
-
-### Camera Access
-
-1. Always check for camera availability
-2. Request permissions explicitly
-3. Handle all error conditions
-4. Provide clear user feedback
-5. Implement proper cleanup
-
-### Performance
-
-1. Optimize camera resolution
-2. Implement proper resource cleanup
-3. Handle camera switching efficiently
-4. Manage memory usage
-
-### User Experience
-
-1. Clear status indicators
-2. Intuitive camera controls
-3. Helpful error messages
-4. Smooth camera switching
-5. Responsive UI feedback
-
-## Future Improvements
-
-### Planned Enhancements
-
-1. Implement Electron camera support
-2. Add advanced camera features
-3. Improve error handling
-4. Enhance user feedback
-5. Optimize performance
-
-### Known Issues
-
-1. Electron camera implementation pending
-2. Some browser compatibility limitations
-3. Platform-specific quirks to address
-
-## Dependencies
-
-### Key Packages
-
-- `@capacitor-mlkit/barcode-scanning`
-- `qrcode-stream`
-- `vue-picture-cropper`
-- Platform-specific camera APIs
-
-## Testing
-
-### Test Scenarios
-
-1. Permission handling
-2. Camera switching
-3. Error conditions
-4. Platform compatibility
-5. Performance metrics
-
-### Test Environment
-
-- Multiple browsers
-- iOS and Android devices
-- Desktop platforms
-- Various network conditions 

.cursor/rules/development_aids.mdc

@@ -1,6 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: true
----
-use the system date function to understand the proper date and time for all interactions.

.cursor/rules/timesafari.mdc

@@ -1,276 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: true
----
----
-description: 
-globs: 
-alwaysApply: true
----
-# Time Safari Context
-
-## Project Overview
-
-Time Safari is an application designed to foster community building through gifts, gratitude, and collaborative projects. The app should make it extremely easy and intuitive for users of any age and capability to recognize contributions, build trust networks, and organize collective action. It is built on services that preserve privacy and data sovereignty.
-
-The ultimate goals of Time Safari are two-fold:
-
-1. **Connect** Make it easy, rewarding, and non-threatening for people to connect with others who have similar interests, and to initiate activities together. This helps people accomplish and learn from other individuals in less-structured environments; moreover, it helps them discover who they want to continue to support and with whom they want to maintain relationships.
-
-2. **Reveal** Widely advertise the great support and rewards that are being given and accepted freely, especially non-monetary ones. Using visuals and text, display the kind of impact that gifts are making in the lives of others. Also show useful and engaging reports of project statistics and personal accomplishments.
-
-
-## Core Approaches
-
-Time Safari should help everyday users build meaningful connections and organize collective efforts by:
-
-1. **Recognizing Contributions**: Creating permanent, verifiable records of gifts and contributions people give to each other and their communities.
-
-2. **Facilitating Collaboration**: Making it ridiculously easy for people to ask for or propose help on projects and interests that matter to them.
-
-3. **Building Trust Networks**: Enabling users to maintain their network and activity visibility. Developing reputation through verified contributions and references, which can be selectively shown to others outside the network.
-
-4. **Preserving Privacy**: Ensuring personal identifiers are only shared with explicitly authorized contacts, allowing private individuals including children to participate safely.
-
-5. **Engaging Content**: Displaying people's records in compelling stories, and highlighting those projects that are lifting people's lives long-term, both in physical support and in emotional-spiritual-creative thriving.
-
-
-## Technical Foundation
-
-This application is built on a privacy-preserving claims architecture (via endorser.ch) with these key characteristics:
-
-- **Decentralized Identifiers (DIDs)**: User identities are based on public/private key pairs stored on their devices
-- **Cryptographic Verification**: All claims and confirmations are cryptographically signed
-- **User-Controlled Visibility**: Users explicitly control who can see their identifiers and data
-- **Merkle-Chained Claims**: Claims are cryptographically chained for verification and integrity
-- **Native and Web App**: Works on Capacitor (iOS, Android), Desktop (Electron and CEFPython), and web browsers
-
-## User Journey
-
-The typical progression of usage follows these stages:
-
-1. **Gratitude & Recognition**: Users begin by expressing and recording gratitude for gifts received, building a foundation of acknowledgment.
-
-2. **Project Proposals**: Users propose projects and ideas, reaching out to connect with others who share similar interests.
-
-3. **Action Triggers**: Offers of help serve as triggers and motivations to execute proposed projects, moving from ideas to action.
-
-## Context for LLM Development
-
-When developing new functionality for Time Safari, consider these design principles:
-
-1. **Accessibility First**: Features should be usable by non-technical users with minimal learning curve.
-
-2. **Privacy by Design**: All features must respect user privacy and data sovereignty.
-
-3. **Progressive Enhancement**: Core functionality should work across all devices, with richer experiences where supported.
-
-4. **Voluntary Collaboration**: The system should enable but never coerce participation.
-
-5. **Trust Building**: Features should help build verifiable trust between users.
-
-6. **Network Effects**: Consider how features scale as more users join the platform.
-
-7. **Low Resource Requirements**: The system should be lightweight enough to run on inexpensive devices users already own.
-
-## Use Cases to Support
-
-LLM development should focus on enhancing these key use cases:
-
-1. **Community Building**: Tools that help people find others with shared interests and values.
-
-2. **Project Coordination**: Features that make it easy to propose collaborative projects and to submit suggestions and offers to existing ones.
-
-3. **Reputation Building**: Methods for users to showcase their contributions and reliability, in contexts where they explicitly reveal that information.
-
-4. **Governance Experimentation**: Features that facilitate decision-making and collective governance.
-
-## Constraints
-
-When developing new features, be mindful of these constraints:
-
-1. **Privacy Preservation**: User identifiers must remain private except when explicitly shared.
-
-2. **Platform Limitations**: Features must work within the constraints of the target app platforms, while aiming to leverage the best platform technology available.
-
-3. **Endorser API Limitations**: Backend features are constrained by the endorser.ch API capabilities.
-
-4. **Performance on Low-End Devices**: The application should remain performant on older/simpler devices.
-
-5. **Offline-First When Possible**: Key functionality should work offline when feasible.
-
-## Project Technologies
-
-- Typescript using ES6 classes using vue-facing-decorator
-- TailwindCSS
-- Vite Build Tool
-- Playwright E2E testing
-- IndexDB
-- Camera, Image uploads, QR Code reader, ...
-
-## Mobile Features
-
-- Deep Linking
-- Local Notifications via a custom Capacitor plugin
-
-## Project Architecture
-
-- The application must work on web browser, PWA (Progressive Web Application), desktop via Electron, and mobile via Capacitor
-- Building for each platform is managed via Vite
-
-## Core Development Principles
-
-### DRY development
-- **Code Reuse**
-  - Extract common functionality into utility functions
-  - Create reusable components for UI patterns
-  - Implement service classes for shared business logic
-  - Use mixins for cross-cutting concerns
-  - Leverage TypeScript interfaces for shared type definitions
-
-- **Component Patterns**
-  - Create base components for common UI elements
-  - Implement higher-order components for shared behavior
-  - Use slot patterns for flexible component composition
-  - Create composable services for business logic
-  - Implement factory patterns for component creation
-
-- **State Management**
-  - Centralize state in Pinia stores
-  - Use computed properties for derived state
-  - Implement shared state selectors
-  - Create reusable state mutations
-  - Use action creators for common operations
-
-- **Error Handling**
-  - Implement centralized error handling
-  - Create reusable error components
-  - Use error boundary components
-  - Implement consistent error logging
-  - Create error type definitions
-
-- **Type Definitions**
-  - Create shared interfaces for common data structures
-  - Use type aliases for complex types
-  - Implement generic types for reusable components
-  - Create utility types for common patterns
-  - Use discriminated unions for state management
-
-- **API Integration**
-  - Create reusable API client classes
-  - Implement request/response interceptors
-  - Use consistent error handling patterns
-  - Create type-safe API endpoints
-  - Implement caching strategies
-
-- **Platform Services**
-  - Abstract platform-specific code behind interfaces
-  - Create platform-agnostic service layers
-  - Implement feature detection
-  - Use dependency injection for services
-  - Create service factories
-
-- **Testing**
-  - Create reusable test utilities
-  - Implement test factories
-  - Use shared test configurations
-  - Create reusable test helpers
-  - Implement consistent test patterns
-  
-### SOLID Principles
-- **Single Responsibility**: Each class/component should have only one reason to change
-  - Components should focus on one specific feature (e.g., QR scanning, DID management)
-  - Services should handle one type of functionality (e.g., platform services, crypto services)
-  - Utilities should provide focused helper functions
-
-- **Open/Closed**: Software entities should be open for extension but closed for modification
-  - Use interfaces for service definitions
-  - Implement plugin architecture for platform-specific features
-  - Allow component behavior extension through props and events
-
-- **Liskov Substitution**: Objects should be replaceable with their subtypes
-  - Platform services should work consistently across web/mobile
-  - Authentication providers should be interchangeable
-  - Storage implementations should be swappable
-
-- **Interface Segregation**: Clients shouldn't depend on interfaces they don't use
-  - Break down large service interfaces into smaller, focused ones
-  - Component props should be minimal and purposeful
-  - Event emissions should be specific and targeted
-
-- **Dependency Inversion**: High-level modules shouldn't depend on low-level modules
-  - Use dependency injection for services
-  - Abstract platform-specific code behind interfaces
-  - Implement factory patterns for component creation
-
-### Law of Demeter
-- Components should only communicate with immediate dependencies
-- Avoid chaining method calls (e.g., `this.service.getUser().getProfile().getName()`)
-- Use mediator patterns for complex component interactions
-- Implement facade patterns for subsystem access
-- Keep component communication through defined events and props
-
-### Composition over Inheritance
-- Prefer building components through composition
-- Use mixins for shared functionality
-- Implement feature toggles through props
-- Create higher-order components for common patterns
-- Use service composition for complex features
-
-### Interface Segregation
-- Define clear interfaces for services
-- Keep component APIs minimal and focused
-- Split large interfaces into smaller, specific ones
-- Use TypeScript interfaces for type definitions
-- Implement role-based interfaces for different use cases
-
-### Fail Fast
-- Validate inputs early in the process
-- Use TypeScript strict mode
-- Implement comprehensive error handling
-- Add runtime checks for critical operations
-- Use assertions for development-time validation
-
-### Principle of Least Astonishment
-- Follow Vue.js conventions consistently
-- Use familiar naming patterns
-- Implement predictable component behaviors
-- Maintain consistent error handling
-- Keep UI interactions intuitive
-
-### Information Hiding
-- Encapsulate implementation details
-- Use private class members
-- Implement proper access modifiers
-- Hide complex logic behind simple interfaces
-- Use TypeScript's access modifiers effectively
-
-### Single Source of Truth
-- Use Pinia for state management
-- Maintain one source for user data
-- Centralize configuration management
-- Use computed properties for derived state
-- Implement proper state synchronization
-
-### Principle of Least Privilege
-- Implement proper access control
-- Use minimal required permissions
-- Follow privacy-by-design principles
-- Restrict component access to necessary data
-- Implement proper authentication/authorization
-
-### Continuous Integration/Continuous Deployment (CI/CD)
-- Automated testing on every commit
-- Consistent build process across platforms
-- Automated deployment pipelines
-- Quality gates for code merging
-- Environment-specific configurations
-
-This expanded documentation provides:
-1. Clear principles for development
-2. Practical implementation guidelines
-3. Real-world examples
-4. TypeScript integration
-5. Best practices for Time Safari
-

.cursor/rules/wa-sqlite.mdc

@@ -1,267 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: true
----
-# wa-sqlite Usage Guide
-
-## Table of Contents
-- [1. Overview](#1-overview)
-- [2. Installation](#2-installation)
-- [3. Basic Setup](#3-basic-setup)
-  - [3.1 Import and Initialize](#31-import-and-initialize)
-  - [3.2 Basic Database Operations](#32-basic-database-operations)
-- [4. Virtual File Systems (VFS)](#4-virtual-file-systems-vfs)
-  - [4.1 Available VFS Options](#41-available-vfs-options)
-  - [4.2 Using a VFS](#42-using-a-vfs)
-- [5. Best Practices](#5-best-practices)
-  - [5.1 Error Handling](#51-error-handling)
-  - [5.2 Transaction Management](#52-transaction-management)
-  - [5.3 Prepared Statements](#53-prepared-statements)
-- [6. Performance Considerations](#6-performance-considerations)
-- [7. Common Issues and Solutions](#7-common-issues-and-solutions)
-- [8. TypeScript Support](#8-typescript-support)
-
-## 1. Overview
-wa-sqlite is a WebAssembly build of SQLite that enables SQLite database operations in web browsers and JavaScript environments. It provides both synchronous and asynchronous builds, with support for custom virtual file systems (VFS) for persistent storage.
-
-## 2. Installation
-```bash
-npm install wa-sqlite
-# or
-yarn add wa-sqlite
-```
-
-## 3. Basic Setup
-
-### 3.1 Import and Initialize
-```javascript
-// Choose one of these imports based on your needs:
-// - wa-sqlite.mjs: Synchronous build
-// - wa-sqlite-async.mjs: Asynchronous build (required for async VFS)
-// - wa-sqlite-jspi.mjs: JSPI-based async build (experimental, Chromium only)
-import SQLiteESMFactory from 'wa-sqlite/dist/wa-sqlite.mjs';
-import * as SQLite from 'wa-sqlite';
-
-async function initDatabase() {
-  // Initialize SQLite module
-  const module = await SQLiteESMFactory();
-  const sqlite3 = SQLite.Factory(module);
-  
-  // Open database (returns a Promise)
-  const db = await sqlite3.open_v2('myDatabase');
-  return { sqlite3, db };
-}
-```
-
-### 3.2 Basic Database Operations
-```javascript
-async function basicOperations() {
-  const { sqlite3, db } = await initDatabase();
-  
-  try {
-    // Create a table
-    await sqlite3.exec(db, `
-      CREATE TABLE IF NOT EXISTS users (
-        id INTEGER PRIMARY KEY,
-        name TEXT NOT NULL,
-        email TEXT UNIQUE
-      )
-    `);
-    
-    // Insert data
-    await sqlite3.exec(db, `
-      INSERT INTO users (name, email) 
-      VALUES ('John Doe', 'john@example.com')
-    `);
-    
-    // Query data
-    const results = [];
-    await sqlite3.exec(db, 'SELECT * FROM users', (row, columns) => {
-      results.push({ row, columns });
-    });
-    
-    return results;
-  } finally {
-    // Always close the database when done
-    await sqlite3.close(db);
-  }
-}
-```
-
-## 4. Virtual File Systems (VFS)
-
-### 4.1 Available VFS Options
-wa-sqlite provides several VFS implementations for persistent storage:
-
-1. **IDBBatchAtomicVFS** (Recommended for general use)
-   - Uses IndexedDB with batch atomic writes
-   - Works in all contexts (Window, Worker, Service Worker)
-   - Supports WAL mode
-   - Best performance with `PRAGMA synchronous=normal`
-
-2. **IDBMirrorVFS**
-   - Keeps files in memory, persists to IndexedDB
-   - Works in all contexts
-   - Good for smaller databases
-
-3. **OPFS-based VFS** (Origin Private File System)
-   - Various implementations available:
-     - AccessHandlePoolVFS
-     - OPFSAdaptiveVFS
-     - OPFSCoopSyncVFS
-     - OPFSPermutedVFS
-   - Better performance but limited to Worker contexts
-
-### 4.2 Using a VFS
-```javascript
-import { IDBBatchAtomicVFS } from 'wa-sqlite/src/examples/IDBBatchAtomicVFS.js';
-import SQLiteESMFactory from 'wa-sqlite/dist/wa-sqlite-async.mjs';
-import * as SQLite from 'wa-sqlite';
-
-async function initDatabaseWithVFS() {
-  const module = await SQLiteESMFactory();
-  const sqlite3 = SQLite.Factory(module);
-  
-  // Register VFS
-  const vfs = await IDBBatchAtomicVFS.create('myApp', module);
-  sqlite3.vfs_register(vfs, true);
-  
-  // Open database with VFS
-  const db = await sqlite3.open_v2('myDatabase');
-  
-  // Configure for better performance
-  await sqlite3.exec(db, 'PRAGMA synchronous = normal');
-  await sqlite3.exec(db, 'PRAGMA journal_mode = WAL');
-  
-  return { sqlite3, db };
-}
-```
-
-## 5. Best Practices
-
-### 5.1 Error Handling
-```javascript
-async function safeDatabaseOperation() {
-  const { sqlite3, db } = await initDatabase();
-  
-  try {
-    await sqlite3.exec(db, 'SELECT * FROM non_existent_table');
-  } catch (error) {
-    if (error.code === SQLite.SQLITE_ERROR) {
-      console.error('SQL error:', error.message);
-    } else {
-      console.error('Database error:', error);
-    }
-  } finally {
-    await sqlite3.close(db);
-  }
-}
-```
-
-### 5.2 Transaction Management
-```javascript
-async function transactionExample() {
-  const { sqlite3, db } = await initDatabase();
-  
-  try {
-    await sqlite3.exec(db, 'BEGIN TRANSACTION');
-    
-    // Perform multiple operations
-    await sqlite3.exec(db, 'INSERT INTO users (name) VALUES (?)', ['Alice']);
-    await sqlite3.exec(db, 'INSERT INTO users (name) VALUES (?)', ['Bob']);
-    
-    await sqlite3.exec(db, 'COMMIT');
-  } catch (error) {
-    await sqlite3.exec(db, 'ROLLBACK');
-    throw error;
-  } finally {
-    await sqlite3.close(db);
-  }
-}
-```
-
-### 5.3 Prepared Statements
-```javascript
-async function preparedStatementExample() {
-  const { sqlite3, db } = await initDatabase();
-  
-  try {
-    // Prepare statement
-    const stmt = await sqlite3.prepare(db, 'SELECT * FROM users WHERE id = ?');
-    
-    // Execute with different parameters
-    await sqlite3.bind(stmt, 1, 1);
-    while (await sqlite3.step(stmt) === SQLite.SQLITE_ROW) {
-      const row = sqlite3.row(stmt);
-      console.log(row);
-    }
-    
-    // Reset and reuse
-    await sqlite3.reset(stmt);
-    await sqlite3.bind(stmt, 1, 2);
-    // ... execute again
-    
-    await sqlite3.finalize(stmt);
-  } finally {
-    await sqlite3.close(db);
-  }
-}
-```
-
-## 6. Performance Considerations
-
-1. **VFS Selection**
-   - Use IDBBatchAtomicVFS for general-purpose applications
-   - Consider OPFS-based VFS for better performance in Worker contexts
-   - Use MemoryVFS for temporary databases
-
-2. **Configuration**
-   - Set appropriate page size (default is usually fine)
-   - Use WAL mode for better concurrency
-   - Consider `PRAGMA synchronous=normal` for better performance
-   - Adjust cache size based on your needs
-
-3. **Concurrency**
-   - Use transactions for multiple operations
-   - Be aware of VFS-specific concurrency limitations
-   - Consider using Web Workers for heavy database operations
-
-## 7. Common Issues and Solutions
-
-1. **Database Locking**
-   - Use appropriate transaction isolation levels
-   - Implement retry logic for busy errors
-   - Consider using WAL mode
-
-2. **Storage Limitations**
-   - Be aware of browser storage quotas
-   - Implement cleanup strategies
-   - Monitor database size
-
-3. **Cross-Context Access**
-   - Use appropriate VFS for your context
-   - Consider message passing for cross-context communication
-   - Be aware of storage access limitations
-
-## 8. TypeScript Support
-wa-sqlite includes TypeScript definitions. The main types are:
-
-```typescript
-type SQLiteCompatibleType = number | string | Uint8Array | Array<number> | bigint | null;
-
-interface SQLiteAPI {
-  open_v2(filename: string, flags?: number, zVfs?: string): Promise<number>;
-  exec(db: number, sql: string, callback?: (row: any[], columns: string[]) => void): Promise<number>;
-  close(db: number): Promise<number>;
-  // ... other methods
-}
-```
-
-## Additional Resources
-
-- [Official GitHub Repository](https://github.com/rhashimoto/wa-sqlite)
-- [Online Demo](https://rhashimoto.github.io/wa-sqlite/demo/)
-- [API Reference](https://rhashimoto.github.io/wa-sqlite/docs/)
-- [FAQ](https://github.com/rhashimoto/wa-sqlite/issues?q=is%3Aissue+label%3Afaq+)
-- [Discussion Forums](https://github.com/rhashimoto/wa-sqlite/discussions) 

.env.development

@@ -2,12 +2,11 @@
 
 # iOS doesn't like spaces in the app title.
 TIME_SAFARI_APP_TITLE="TimeSafari_Dev"
-VITE_APP_SERVER=http://localhost:8080
+VITE_APP_SERVER=http://localhost:3000
 # This is the claim ID for actions in the BVC project, with the JWT ID on this environment (not production).
 VITE_BVC_MEETUPS_PROJECT_CLAIM_ID=https://endorser.ch/entity/01HWE8FWHQ1YGP7GFZYYPS272F
 VITE_DEFAULT_ENDORSER_API_SERVER=http://localhost:3000
 # Using shared server by default to ease setup, which works for shared test users.
 VITE_DEFAULT_IMAGE_API_SERVER=https://test-image-api.timesafari.app
 VITE_DEFAULT_PARTNER_API_SERVER=http://localhost:3000
-#VITE_DEFAULT_PUSH_SERVER... can't be set up with localhost domain
 VITE_PASSKEYS_ENABLED=true

.env.example

@@ -0,0 +1,6 @@
+# Admin DID credentials
+ADMIN_DID=did:ethr:0x0000694B58C2cC69658993A90D3840C560f2F51F
+ADMIN_PRIVATE_KEY=2b6472c026ec2aa2c4235c994a63868fc9212d18b58f6cbfe861b52e71330f5b
+
+# API Configuration
+ENDORSER_API_URL=https://test-api.endorser.ch/api/v2/claim 

.env.production

@@ -9,4 +9,3 @@ VITE_DEFAULT_ENDORSER_API_SERVER=https://api.endorser.ch
 
 VITE_DEFAULT_IMAGE_API_SERVER=https://image-api.timesafari.app
 VITE_DEFAULT_PARTNER_API_SERVER=https://partner-api.endorser.ch
-VITE_DEFAULT_PUSH_SERVER=https://timesafari.app

.env.staging

@@ -9,5 +9,4 @@ VITE_DEFAULT_ENDORSER_API_SERVER=https://test-api.endorser.ch
 
 VITE_DEFAULT_IMAGE_API_SERVER=https://test-image-api.timesafari.app
 VITE_DEFAULT_PARTNER_API_SERVER=https://test-partner-api.endorser.ch
-VITE_DEFAULT_PUSH_SERVER=https://test.timesafari.app
 VITE_PASSKEYS_ENABLED=true

.eslintrc.js

@@ -4,12 +4,6 @@ module.exports = {
     node: true,
     es2022: true,
   },
-  ignorePatterns: [
-    'node_modules/',
-    'dist/',
-    'dist-electron/',
-    '*.d.ts'
-  ],
   extends: [
     "plugin:vue/vue3-recommended",
     "eslint:recommended",

.gitignore

@@ -42,7 +42,7 @@ dist-electron-packages
 .ruby-version
 +.env
 
-# Test files generated by scripts test-ios.js & test-android.js
+# Generated test files
 .generated/
 
 .env.default
@@ -51,7 +51,7 @@ vendor/
 # Build logs
 build_logs/
 
-# PWA icon files generated by capacitor-assets
-icons
-
-
+android/app/src/main/assets/public
+android/app/src/main/res
+android/.gradle/buildOutputCleanup/buildOutputCleanup.lock
+android/.gradle/file-system.probe

BUILDING.md

@@ -9,6 +9,19 @@ For a quick dev environment setup, use [pkgx](https://pkgx.dev).
 - Node.js (LTS version recommended)
 - npm (comes with Node.js)
 - Git
+- For Android builds: Android Studio with SDK installed
+- For iOS builds: macOS with Xcode and ruby gems & bundle
+  - pkgx +rubygems.org sh
+
+  - ... and you may have to fix these, especially with pkgx
+
+   ```bash
+   gem_path=$(which gem)
+   shortened_path="${gem_path:h:h}"
+   export GEM_HOME=$shortened_path
+   export GEM_PATH=$shortened_path
+   ```
+
 - For desktop builds: Additional build tools based on your OS
 
 ## Forks
@@ -41,7 +54,7 @@ Install dependencies:
 1. Run the production build:
 
    ```bash
-   npm run build:web
+   npm run build
    ```
 
    The built files will be in the `dist` directory.
@@ -71,7 +84,7 @@ Install dependencies:
 * For test, build the app (because test server is not yet set up to build):
 
 ```bash
-TIME_SAFARI_APP_TITLE="TimeSafari_Test" VITE_APP_SERVER=https://test.timesafari.app VITE_BVC_MEETUPS_PROJECT_CLAIM_ID=https://endorser.ch/entity/01HWE8FWHQ1YGP7GFZYYPS272F VITE_DEFAULT_ENDORSER_API_SERVER=https://test-api.endorser.ch VITE_DEFAULT_IMAGE_API_SERVER=https://test-image-api.timesafari.app VITE_DEFAULT_PARTNER_API_SERVER=https://test-partner-api.endorser.ch VITE_DEFAULT_PUSH_SERVER=https://test.timesafari.app VITE_PASSKEYS_ENABLED=true npm run build
+TIME_SAFARI_APP_TITLE="TimeSafari_Test" VITE_APP_SERVER=https://test.timesafari.app VITE_BVC_MEETUPS_PROJECT_CLAIM_ID=https://endorser.ch/entity/01HWE8FWHQ1YGP7GFZYYPS272F VITE_DEFAULT_ENDORSER_API_SERVER=https://test-api.endorser.ch VITE_DEFAULT_IMAGE_API_SERVER=https://test-image-api.timesafari.app VITE_DEFAULT_PARTNER_API_SERVER=https://test-partner-api.endorser.ch VITE_PASSKEYS_ENABLED=true npm run build
 ```
 
    ... and transfer to the test server:
@@ -98,106 +111,8 @@ TIME_SAFARI_APP_TITLE="TimeSafari_Test" VITE_APP_SERVER=https://test.timesafari.
 
 * Record the new hash in the changelog. Edit package.json to increment version & add "-beta", `npm install`, and commit. Also record what version is on production.
 
-## Docker Deployment
 
-The application can be containerized using Docker for consistent deployment across environments.
 
-### Prerequisites
-
-- Docker installed on your system
-- Docker Compose (optional, for multi-container setups)
-
-### Building the Docker Image
-
-1. Build the Docker image:
-
-   ```bash
-   docker build -t timesafari:latest .
-   ```
-
-2. For development builds with specific environment variables:
-
-   ```bash
-   docker build --build-arg NODE_ENV=development -t timesafari:dev .
-   ```
-
-### Running the Container
-
-1. Run the container:
-
-   ```bash
-   docker run -d -p 80:80 timesafari:latest
-   ```
-
-2. For development with hot-reloading:
-
-   ```bash
-   docker run -d -p 80:80 -v $(pwd):/app timesafari:dev
-   ```
-
-### Using Docker Compose
-
-Create a `docker-compose.yml` file:
-
-```yaml
-version: '3.8'
-services:
-  timesafari:
-    build: .
-    ports:
-      - "80:80"
-    environment:
-      - NODE_ENV=production
-    restart: unless-stopped
-```
-
-Run with Docker Compose:
-
-```bash
-docker-compose up -d
-```
-
-### Production Deployment
-
-For production deployment, consider the following:
-
-1. Use specific version tags instead of 'latest'
-2. Implement health checks
-3. Configure proper logging
-4. Set up reverse proxy with SSL termination
-5. Use Docker secrets for sensitive data
-
-Example production deployment:
-
-```bash
-# Build with specific version
-docker build -t timesafari:1.0.0 .
-
-# Run with production settings
-docker run -d \
-  --name timesafari \
-  -p 80:80 \
-  --restart unless-stopped \
-  -e NODE_ENV=production \
-  timesafari:1.0.0
-```
-
-### Troubleshooting Docker
-
-1. **Container fails to start**
-   - Check logs: `docker logs <container_id>`
-   - Verify port availability
-   - Check environment variables
-
-2. **Build fails**
-   - Ensure all dependencies are in package.json
-   - Check Dockerfile syntax
-   - Verify build context
-
-3. **Performance issues**
-   - Monitor container resources: `docker stats`
-   - Check nginx configuration
-   - Verify caching settings
 
 ## Desktop Build (Electron)
 
@@ -223,77 +138,21 @@ docker run -d \
    - AppImage: `dist-electron-packages/TimeSafari-x.x.x.AppImage`
    - DEB: `dist-electron-packages/timesafari_x.x.x_amd64.deb`
 
-### macOS Build
-
-1. Build the electron app in production mode:
-
-   ```bash
-   npm run build:web
-   npm run build:electron
-   npm run electron:build-mac
-   ```
-
-2. Package the Electron app for macOS:
-
-   ```bash
-   # For Intel Macs
-   npm run electron:build-mac
-
-   # For Universal build (Intel + Apple Silicon)
-   npm run electron:build-mac-universal
-   ```
-
-3. The packaged applications will be in `dist-electron-packages/`:
-   - `.app` bundle: `TimeSafari.app`
-   - `.dmg` installer: `TimeSafari-x.x.x.dmg`
-   - `.zip` archive: `TimeSafari-x.x.x-mac.zip`
-
-### Code Signing and Notarization (macOS)
-
-For public distribution on macOS, you need to code sign and notarize your app:
-
-1. Set up environment variables:
-   ```bash
-   export CSC_LINK=/path/to/your/certificate.p12
-   export CSC_KEY_PASSWORD=your_certificate_password
-   export APPLE_ID=your_apple_id
-   export APPLE_ID_PASSWORD=your_app_specific_password
-   ```
-
-2. Build with signing:
-   ```bash
-   npm run electron:build-mac
-   ```
-
 ### Running the Packaged App
 
-- **Linux**:
-  - AppImage: Make executable and run
-    ```bash
-    chmod +x dist-electron-packages/TimeSafari-*.AppImage
-    ./dist-electron-packages/TimeSafari-*.AppImage
-    ```
-  - DEB: Install and run
-    ```bash
-    sudo dpkg -i dist-electron-packages/timesafari_*_amd64.deb
-    timesafari
-    ```
+- AppImage: Make executable and run
 
-- **macOS**:
-  - `.app` bundle: Double-click `TimeSafari.app` in Finder
-  - `.dmg` installer:
-    1. Double-click the `.dmg` file
-    2. Drag the app to your Applications folder
-    3. Launch from Applications
-  - `.zip` archive:
-    1. Extract the `.zip` file
-    2. Move `TimeSafari.app` to your Applications folder
-    3. Launch from Applications
+  ```bash
+  chmod +x dist-electron-packages/TimeSafari-*.AppImage
+  ./dist-electron-packages/TimeSafari-*.AppImage
+  ```
 
-  Note: If you get a security warning when running the app:
-  1. Right-click the app
-  2. Select "Open"
-  3. Click "Open" in the security dialog
+- DEB: Install and run
+
+  ```bash
+  sudo dpkg -i dist-electron-packages/timesafari_*_amd64.deb
+  timesafari
+  ```
 
 ### Development Testing
 
@@ -313,99 +172,42 @@ npm run build:electron-prod && npm run electron:start
 
 Prerequisites: macOS with Xcode installed
 
-#### First-time iOS Configuration
-
-- Generate certificates inside XCode.
-
-- Right-click on App and under Signing & Capabilities set the Team.
-
-#### Each Release
-
-0. First time (or if XCode dependencies change):
-
-  - `pkgx +rubygems.org sh`
-
-  - ... and you may have to fix these, especially with pkgx
-
-   ```bash
-   gem_path=$(which gem)
-   shortened_path="${gem_path:h:h}"
-   export GEM_HOME=$shortened_path
-   export GEM_PATH=$shortened_path
-   ```
-
-   ```bash
-   cd ios/App
-   pod install
-   ```
-
 1. Build the web assets:
 
    ```bash
-   rm -rf dist
-   npm run build:web
    npm run build:capacitor
    ```
 
-
 2. Update iOS project with latest build:
 
    ```bash
    npx cap sync ios
    ```
 
-  - If that fails with "Could not find..." then look at the "gem_path" instructions above.
-
 3. Copy the assets:
 
    ```bash
-   # It makes no sense why capacitor-assets will not run without these but it actually changes the contents.
    mkdir -p ios/App/App/Assets.xcassets/AppIcon.appiconset
-   echo '{"images":[]}' > ios/App/App/Assets.xcassets/AppIcon.appiconset/Contents.json
-   mkdir -p ios/App/App/Assets.xcassets/Splash.imageset
-   echo '{"images":[]}' > ios/App/App/Assets.xcassets/Splash.imageset/Contents.json
    npx capacitor-assets generate --ios
    ```
 
-4. Bump the version to match Android:
-
-   ```
-   cd ios/App
-   xcrun agvtool new-version 25
-   # Unfortunately this edits Info.plist directly.
-   #xcrun agvtool new-marketing-version 0.4.5
-   cat App.xcodeproj/project.pbxproj | sed "s/MARKETING_VERSION = .*;/MARKETING_VERSION = 0.5.1;/g" > temp
-   mv temp App.xcodeproj/project.pbxproj
-   cd -
-   ```
-
-5. Open the project in Xcode:
+3. Open the project in Xcode:
 
    ```bash
    npx cap open ios
    ```
 
-6. Use Xcode to build and run on simulator or device.
+4. Use Xcode to build and run on simulator or device.
 
-  * Select Product -> Destination with some Simulator version. Then click the run arrow.
+#### First-time iOS Configuration
 
-7. Release
+- Generate certificates inside XCode.
 
-  * Someday: Under "General" we want to rename a bunch of things to "Time Safari"
-  * Choose Product -> Destination -> Any iOS Device
-  * Choose Product -> Archive
-    * This will trigger a build and take time, needing user's "login" keychain password (user's login password), repeatedly.
-    * If it fails with `building for 'iOS', but linking in dylib (.../.pkgx/zlib.net/v1.3.0/lib/libz.1.3.dylib) built for 'macOS'` then run XCode outside that terminal (ie. not with `npx cap open ios`).
-    * Click Distribute -> App Store Connect
-  * In AppStoreConnect, add the build to the distribution: remove the current build with the "-" when you hover over it, then "Add Build" with the new build.
-    * May have to go to App Review, click Submission, then hover over the build and click "-".
-    * It can take 15 minutes for the build to show up in the list of builds.
-    * You'll probably have to "Manage" something about encryption, disallowed in France.
-    * Then "Save" and "Add to Review" and "Resubmit to App Review".
+- Right-click on App and under Signing & Capabilities set the Team.
 
 ### Android Build
 
-Prerequisites: Android Studio with Java SDK installed
+Prerequisites: Android Studio with SDK installed
 
 1. Build the web assets:
 
@@ -427,15 +229,13 @@ Prerequisites: Android Studio with Java SDK installed
    npx capacitor-assets generate --android
    ```
 
-4. Bump version to match iOS: android/app/build.gradle
-
-5. Open the project in Android Studio:
+4. Open the project in Android Studio:
 
    ```bash
    npx cap open android
    ```
 
-6. Use Android Studio to build and run on emulator or device.
+5. Use Android Studio to build and run on emulator or device.
 
 ## Android Build from the console
 
@@ -443,7 +243,7 @@ Prerequisites: Android Studio with Java SDK installed
    cd android
    ./gradlew clean
    ./gradlew build -Dlint.baselines.continue=true
-   cd -
+   cd ..
    npx cap run android
    ```
 
@@ -453,29 +253,12 @@ Prerequisites: Android Studio with Java SDK installed
    ./gradlew bundleDebug -Dlint.baselines.continue=true
    ```
 
-... or, to create a signed release:
-
-  * Setup by adding the app/gradle.properties.secrets file (see properties at top of app/build.gradle) and the app/time-safari-upload-key-pkcs12.jks file
-  * In app/build.gradle, bump the versionCode and maybe the versionName
-  * Then `bundleRelease`:
+... or, to create a signed release, add the app/gradle.properties.secrets file (see properties at top of app/build.gradle) and the app/time-safari-upload-key-pkcs12.jks file, then `bundleRelease`:
 
    ```bash
-   cd android
    ./gradlew bundleRelease -Dlint.baselines.continue=true
-   cd -
    ```
 
-  ... and find your `aab` file at app/build/outputs/bundle/release
-
-At play.google.com/console:
-
-- Go to the Testing Track (eg. Closed).
-- Click "Create new release".
-- Upload the `aab` file.
-- Hit "Next".
-- Save, go to "Publishing Overview" as prompted, and click "Send changes for review".
-
-- Note that if you add testers, you have to go to "Publishing Overview" and send those changes or your (closed) testers won't see it.
 
 
 ## First-time Android Configuration for deep links
@@ -489,4 +272,253 @@ You must add the following intent filter to the `android/app/src/main/AndroidMan
                   <category android:name="android.intent.category.BROWSABLE" />
                   <data android:scheme="timesafari" />
                </intent-filter>
-   ```
+   ```
+
+You must also add the following to the `android/app/build.gradle` file:
+
+   ```gradle
+   android {
+      // ... existing config ...
+
+      lintOptions {
+         disable 'UnsanitizedFilenameFromContentProvider'
+         abortOnError false
+         baseline file("lint-baseline.xml")
+         
+         // Ignore Capacitor module issues
+         ignore 'DefaultLocale'
+         ignore 'UnsanitizedFilenameFromContentProvider'
+         ignore 'LintBaseline'
+         ignore 'LintBaselineFixed'
+      }
+   }
+   ```
+
+Modify `/android/build.gradle` to use a stable version of AGP and make sure Kotlin version is compatible.
+
+   ```gradle
+   buildscript {
+      repositories {
+         google()
+         mavenCentral()
+      }
+      dependencies {
+         // Use a stable version of AGP
+         classpath 'com.android.tools.build:gradle:8.1.0'
+         
+         // Make sure Kotlin version is compatible
+         classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.8.0"
+      }
+   }
+
+   allprojects {
+      repositories {
+         google()
+         mavenCentral()
+      }
+   }
+
+   // Add this to handle version conflicts
+   configurations.all {
+      resolutionStrategy {
+         force 'org.jetbrains.kotlin:kotlin-stdlib:1.8.0'
+         force 'org.jetbrains.kotlin:kotlin-stdlib-common:1.8.0'
+      }
+   }
+   ```
+
+## PyWebView Desktop Build
+
+### Prerequisites for PyWebView
+
+- Python 3.8 or higher
+- pip (Python package manager)
+- virtualenv (recommended)
+- System dependencies:
+
+  ```bash
+  # For Ubuntu/Debian
+  sudo apt-get install python3-webview
+  # or
+  sudo apt-get install python3-gi python3-gi-cairo gir1.2-gtk-3.0 gir1.2-webkit2-4.0
+
+  # For Arch Linux
+  sudo pacman -S webkit2gtk python-gobject python-cairo
+
+  # For Fedora
+  sudo dnf install python3-webview
+  # or
+  sudo dnf install python3-gobject python3-cairo webkit2gtk3
+  ```
+
+### Setup
+
+1. Create and activate a virtual environment (recommended):
+
+   ```bash
+   python -m venv .venv
+   source .venv/bin/activate  # On Linux/macOS
+   # or
+   .venv\Scripts\activate     # On Windows
+   ```
+
+2. Install Python dependencies:
+
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+### Troubleshooting
+
+If encountering PyInstaller version errors:
+
+```bash
+# Try installing the latest stable version
+pip install --upgrade pyinstaller
+```
+
+### Development of PyWebView
+
+1. Start the PyWebView development build:
+
+   ```bash
+   npm run pywebview:dev
+   ```
+
+### Building for Distribution
+
+#### Linux
+
+```bash
+npm run pywebview:package-linux
+```
+
+The packaged application will be in `dist/TimeSafari`
+
+#### Windows
+
+```bash
+npm run pywebview:package-win
+```
+
+The packaged application will be in `dist/TimeSafari`
+
+#### macOS
+
+```bash
+npm run pywebview:package-mac
+```
+
+The packaged application will be in `dist/TimeSafari`
+
+## Testing
+
+Run all tests (requires XCode and Android Studio/device):
+
+```bash
+npm run test:all
+```
+
+See [TESTING.md](test-playwright/TESTING.md) for more details.
+
+## Linting
+
+Check code style:
+
+```bash
+npm run lint
+```
+
+Fix code style issues:
+
+```bash
+npm run lint-fix
+```
+
+## Environment Configuration
+
+See `.env.*` files for configuration.
+
+## Notes
+
+- The application uses PWA (Progressive Web App) features for web builds
+- Electron builds disable PWA features automatically
+- Build output directories:
+  - Web: `dist/`
+  - Electron: `dist-electron/`
+  - Capacitor: `dist-capacitor/`
+
+## Deployment
+
+### Version Management
+
+1. Update CHANGELOG.md with new changes
+2. Update version in package.json
+3. Commit changes and tag release:
+
+   ```bash
+   git tag <VERSION_TAG>
+   git push origin <VERSION_TAG>
+   ```
+
+4. After deployment, update package.json with next version + "-beta"
+
+### Test Server
+
+```bash
+# Build using staging environment
+npm run build -- --mode staging
+
+# Deploy to test server
+rsync -azvu -e "ssh -i ~/.ssh/<YOUR_KEY>" dist ubuntutest@test.timesafari.app:time-safari/
+```
+
+### Production Server
+
+```bash
+# On the production server:
+pkgx +npm sh
+cd crowd-funder-for-time-pwa
+git checkout master && git pull
+git checkout <VERSION_TAG>
+npm install
+npm run build
+cd -
+
+# Backup and deploy
+mv time-safari/dist time-safari-dist-prev.0 && mv crowd-funder-for-time-pwa/dist time-safari/
+```
+
+## Troubleshooting Builds
+
+### Common Build Issues
+
+1. **Missing Environment Variables**
+   - Check that all required variables are set in your .env file
+   - For development, ensure local services are running on correct ports
+
+2. **Electron Build Failures**
+   - Verify Node.js version compatibility
+   - Check that all required dependencies are installed
+   - Ensure proper paths in electron/main.js
+
+3. **Mobile Build Issues**
+   - For iOS: Xcode command line tools must be installed
+   - For Android: Correct SDK version must be installed
+   - Check Capacitor configuration in capacitor.config.ts
+
+
+# List all installed packages
+adb shell pm list packages | grep timesafari
+
+# Force stop the app (if it's running)
+adb shell am force-stop app.timesafari
+
+# Clear app data (if you don't want to fully uninstall)
+adb shell pm clear app.timesafari
+
+# Uninstall for all users
+adb shell pm uninstall -k --user 0 app.timesafari
+
+# Check if app is installed
+adb shell pm path app.timesafari

CEFPython-Survey.md

@@ -1,538 +0,0 @@
-# CEFPython Implementation Survey for TimeSafari
-
-**Author:** Matthew Raymer  
-**Date:** December 2025  
-**Project:** TimeSafari Cross-Platform Desktop Implementation
-
-## Executive Summary
-
-This survey evaluates implementing CEFPython as an additional desktop platform for TimeSafari, with full integration into the existing migration system used by Capacitor and native web platforms.
-
-### Key Findings
-
-**Feasibility:** ✅ **Highly Feasible** - CEFPython can integrate seamlessly with TimeSafari's existing architecture
-
-**Migration System Compatibility:** ✅ **Full Compatibility** - Can use the exact same `migration.ts` system as Capacitor and web
-
-**Performance:** ✅ **Excellent** - Native Python backend with Chromium rendering engine
-
-**Security:** ✅ **Strong** - Chromium's security model with Python backend isolation
-
----
-
-## 1. Architecture Overview
-
-### 1.1 Current Platform Architecture
-
-TimeSafari uses a sophisticated cross-platform architecture with shared codebase and platform-specific implementations:
-
-```typescript
-src/
-├── main.common.ts          # Shared initialization
-├── main.web.ts            # Web/PWA entry point
-├── main.capacitor.ts      # Mobile entry point  
-├── main.electron.ts       # Electron entry point
-├── main.pywebview.ts      # PyWebView entry point
-├── main.cefpython.ts      # NEW: CEFPython entry point
-├── services/
-│   ├── PlatformService.ts # Platform abstraction interface
-│   ├── PlatformServiceFactory.ts
-│   └── platforms/
-│       ├── WebPlatformService.ts
-│       ├── CapacitorPlatformService.ts
-│       ├── ElectronPlatformService.ts
-│       ├── PyWebViewPlatformService.ts
-│       └── CEFPythonPlatformService.ts  # NEW
-└── cefpython/             # NEW: CEFPython backend
-    ├── main.py
-    ├── handlers/
-    │   ├── database.py    # SQLite with migration support
-    │   ├── crypto.py      # Cryptographic operations
-    │   └── api.py         # API server integration
-    └── bridge/
-        └── javascript_bridge.py  # JS-Python communication
-```
-
-### 1.2 Migration System Integration
-
-**Key Insight:** CEFPython can use the exact same migration system as Capacitor and web platforms:
-
-```typescript
-// src/main.cefpython.ts - CEFPython entry point
-import { initializeApp } from "./main.common";
-import { runMigrations } from "./db-sql/migration";
-import { CEFPythonPlatformService } from "./services/platforms/CEFPythonPlatformService";
-
-const app = initializeApp();
-
-// Initialize CEFPython platform service
-const platformService = new CEFPythonPlatformService();
-
-// Run migrations using the same system as Capacitor
-async function initializeDatabase() {
-  const sqlExec = (sql: string) => platformService.dbExecute(sql);
-  const sqlQuery = (sql: string) => platformService.dbQuery(sql);
-  const extractMigrationNames = (result: any) => {
-    const names = result.values?.map((row: any) => row.name) || [];
-    return new Set(names);
-  };
-  
-  await runMigrations(sqlExec, sqlQuery, extractMigrationNames);
-}
-
-// Initialize database before mounting app
-initializeDatabase().then(() => {
-  app.mount("#app");
-});
-```
-
----
-
-## 2. Python Backend Implementation
-
-### 2.1 Database Handler with Migration Support
-
-```python
-# src/cefpython/handlers/database.py
-import sqlite3
-from pathlib import Path
-from typing import List, Dict, Any
-
-class DatabaseHandler:
-    def __init__(self):
-        self.db_path = self._get_db_path()
-        self.connection = sqlite3.connect(str(self.db_path))
-        self.connection.row_factory = sqlite3.Row
-        
-        # Configure for better performance
-        self.connection.execute("PRAGMA journal_mode=WAL;")
-        self.connection.execute("PRAGMA synchronous=NORMAL;")
-    
-    def query(self, sql: str, params: List[Any] = None) -> Dict[str, Any]:
-        """Execute SQL query and return results in Capacitor-compatible format"""
-        cursor = self.connection.cursor()
-        
-        if params:
-            cursor.execute(sql, params)
-        else:
-            cursor.execute(sql)
-        
-        if sql.strip().upper().startswith('SELECT'):
-            columns = [description[0] for description in cursor.description]
-            rows = []
-            for row in cursor.fetchall():
-                rows.append(dict(zip(columns, row)))
-            return {'values': rows}  # Match Capacitor format
-        else:
-            self.connection.commit()
-            return {'affected_rows': cursor.rowcount}
-    
-    def execute(self, sql: string, params: List[Any] = None) -> Dict[str, Any]:
-        """Execute SQL statement (for INSERT, UPDATE, DELETE, CREATE)"""
-        cursor = self.connection.cursor()
-        
-        if params:
-            cursor.execute(sql, params)
-        else:
-            cursor.execute(sql)
-        
-        self.connection.commit()
-        
-        return {
-            'changes': {
-                'changes': cursor.rowcount,
-                'lastId': cursor.lastrowid
-            }
-        }
-```
-
-### 2.2 Platform Service Implementation
-
-```typescript
-// src/services/platforms/CEFPythonPlatformService.ts
-import { PlatformService } from '../PlatformService';
-import { runMigrations } from '@/db-sql/migration';
-
-export class CEFPythonPlatformService implements PlatformService {
-  private bridge: any;
-
-  constructor() {
-    this.bridge = (window as any).cefBridge;
-    if (!this.bridge) {
-      throw new Error('CEFPython bridge not available');
-    }
-  }
-
-  // Database operations using the same interface as Capacitor
-  async dbQuery(sql: string, params?: any[]): Promise<any> {
-    const result = await this.bridge.call('database', 'query', sql, params || []);
-    return result;
-  }
-
-  async dbExecute(sql: string, params?: any[]): Promise<any> {
-    const result = await this.bridge.call('database', 'execute', sql, params || []);
-    return result;
-  }
-
-  // Migration system integration
-  async runMigrations(): Promise<void> {
-    const sqlExec: (sql: string) => Promise<any> = this.dbExecute.bind(this);
-    const sqlQuery: (sql: string) => Promise<any> = this.dbQuery.bind(this);
-    const extractMigrationNames: (result: any) => Set<string> = (result) => {
-      const names = result.values?.map((row: any) => row.name) || [];
-      return new Set(names);
-    };
-    
-    await runMigrations(sqlExec, sqlQuery, extractMigrationNames);
-  }
-
-  // Platform detection
-  isCEFPython(): boolean {
-    return true;
-  }
-
-  getCapabilities(): PlatformCapabilities {
-    return {
-      hasCamera: true,
-      hasFileSystem: true,
-      hasNotifications: true,
-      hasSQLite: true,
-      hasCrypto: true
-    };
-  }
-}
-```
-
----
-
-## 3. Migration System Compatibility
-
-### 3.1 Key Advantage
-
-**CEFPython can use the exact same migration system as Capacitor:**
-
-```typescript
-// Both Capacitor and CEFPython use the same migration.ts
-import { runMigrations } from '@/db-sql/migration';
-
-// Capacitor implementation
-const sqlExec: (sql: string) => Promise<capSQLiteChanges> = this.db.execute.bind(this.db);
-const sqlQuery: (sql: string) => Promise<DBSQLiteValues> = this.db.query.bind(this.db);
-
-// CEFPython implementation  
-const sqlExec: (sql: string) => Promise<any> = this.dbExecute.bind(this);
-const sqlQuery: (sql: string) => Promise<any> = this.dbQuery.bind(this);
-
-// Both use the same migration runner
-await runMigrations(sqlExec, sqlQuery, extractMigrationNames);
-```
-
-### 3.2 Database Format Compatibility
-
-The Python database handler returns data in the same format as Capacitor:
-
-```python
-# Python returns Capacitor-compatible format
-def query(self, sql: str, params: List[Any] = None) -> Dict[str, Any]:
-    # ... execute query ...
-    return {
-        'values': [
-            {'name': '001_initial', 'executed_at': '2025-01-01'},
-            {'name': '002_add_contacts', 'executed_at': '2025-01-02'}
-        ]
-    }
-```
-
-This matches the Capacitor format:
-```typescript
-// Capacitor returns same format
-const result = await this.db.query("SELECT name FROM migrations");
-// result = { values: [{ name: '001_initial' }, { name: '002_add_contacts' }] }
-```
-
----
-
-## 4. Build Configuration
-
-### 4.1 Vite Configuration
-
-```typescript
-// vite.config.cefpython.mts
-import { defineConfig } from 'vite';
-import { createBuildConfig } from './vite.config.common.mts';
-
-export default defineConfig({
-  ...createBuildConfig('cefpython'),
-  
-  define: {
-    'process.env.VITE_PLATFORM': JSON.stringify('cefpython'),
-    'process.env.VITE_PWA_ENABLED': JSON.stringify(false),
-    __IS_MOBILE__: JSON.stringify(false),
-    __USE_QR_READER__: JSON.stringify(true)
-  }
-});
-```
-
-### 4.2 Package.json Scripts
-
-```json
-{
-  "scripts": {
-    "build:cefpython": "vite build --config vite.config.cefpython.mts",
-    "dev:cefpython": "concurrently \"npm run dev:web\" \"python src/cefpython/main.py --dev\"",
-    "test:cefpython": "python -m pytest tests/cefpython/"
-  }
-}
-```
-
-### 4.3 Python Requirements
-
-```txt
-# requirements-cefpython.txt
-cefpython3>=66.1
-cryptography>=3.4.0
-requests>=2.25.0
-pyinstaller>=4.0
-pytest>=6.0.0
-```
-
----
-
-## 5. Platform Service Factory Integration
-
-### 5.1 Updated Factory
-
-```typescript
-// src/services/PlatformServiceFactory.ts
-import { CEFPythonPlatformService } from './platforms/CEFPythonPlatformService';
-
-export function createPlatformService(platform: string): PlatformService {
-  switch (platform) {
-    case 'web':
-      return new WebPlatformService();
-    case 'capacitor':
-      return new CapacitorPlatformService();
-    case 'electron':
-      return new ElectronPlatformService();
-    case 'pywebview':
-      return new PyWebViewPlatformService();
-    case 'cefpython':
-      return new CEFPythonPlatformService();  // NEW
-    default:
-      throw new Error(`Unsupported platform: ${platform}`);
-  }
-}
-```
-
----
-
-## 6. Performance and Security Analysis
-
-### 6.1 Performance Comparison
-
-| Metric | Electron | PyWebView | CEFPython | Notes |
-|--------|----------|-----------|-----------|-------|
-| **Memory Usage** | 150-200MB | 80-120MB | 100-150MB | CEFPython more efficient than Electron |
-| **Startup Time** | 3-5s | 2-3s | 2-4s | Similar to PyWebView |
-| **Database Performance** | Good | Good | Excellent | Native SQLite |
-| **Crypto Performance** | Good | Good | Excellent | Native Python crypto |
-| **Bundle Size** | 120-150MB | 50-80MB | 80-120MB | Smaller than Electron |
-
-### 6.2 Security Features
-
-```python
-# src/cefpython/utils/security.py
-class SecurityManager:
-    def __init__(self):
-        self.blocked_domains = set(['malicious-site.com'])
-        self.allowed_schemes = {'https', 'http', 'file'}
-    
-    def validate_network_access(self, url: str) -> bool:
-        """Validate if network access is allowed"""
-        from urllib.parse import urlparse
-        parsed = urlparse(url)
-        
-        # Check blocked domains
-        if parsed.hostname in self.blocked_domains:
-            return False
-        
-        # Allow HTTPS only for external domains
-        if parsed.scheme != 'https' and parsed.hostname != 'localhost':
-            return False
-        
-        return True
-```
-
----
-
-## 7. Migration Strategy
-
-### 7.1 Phase 1: Foundation (Week 1-2)
-
-**Objectives:**
-- Set up CEFPython development environment
-- Create basic application structure
-- Implement database handler with migration support
-- Establish JavaScript-Python bridge
-
-**Deliverables:**
-- [ ] Basic CEFPython application that loads TimeSafari web app
-- [ ] Database handler with SQLite integration
-- [ ] Migration system integration
-- [ ] JavaScript bridge for communication
-
-### 7.2 Phase 2: Platform Integration (Week 3-4)
-
-**Objectives:**
-- Implement CEFPython platform service
-- Integrate with existing migration system
-- Test database operations with real data
-- Validate migration compatibility
-
-**Deliverables:**
-- [ ] CEFPython platform service implementation
-- [ ] Migration system integration
-- [ ] Database compatibility testing
-- [ ] Performance benchmarking
-
-### 7.3 Phase 3: Feature Integration (Week 5-6)
-
-**Objectives:**
-- Integrate with existing platform features
-- Implement API server integration
-- Add security features
-- Test with real user workflows
-
-**Deliverables:**
-- [ ] Full feature compatibility
-- [ ] API integration
-- [ ] Security implementation
-- [ ] User workflow testing
-
-### 7.4 Phase 4: Polish and Distribution (Week 7-8)
-
-**Objectives:**
-- Optimize performance
-- Add build and distribution scripts
-- Create documentation
-- Prepare for release
-
-**Deliverables:**
-- [ ] Performance optimization
-- [ ] Build automation
-- [ ] Documentation
-- [ ] Release-ready application
-
----
-
-## 8. Risk Assessment
-
-### 8.1 Technical Risks
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| **CEFPython compatibility issues** | Medium | High | Use stable CEFPython version, test thoroughly |
-| **Migration system integration** | Low | High | Follow existing patterns, extensive testing |
-| **Performance issues** | Low | Medium | Benchmark early, optimize as needed |
-| **Security vulnerabilities** | Low | High | Implement security manager, regular audits |
-
-### 8.2 Development Risks
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| **Python/CEF knowledge gap** | Medium | Medium | Training, documentation, pair programming |
-| **Integration complexity** | Medium | Medium | Incremental development, extensive testing |
-| **Build system complexity** | Low | Medium | Automated build scripts, CI/CD |
-
----
-
-## 9. Success Metrics
-
-### 9.1 Technical Metrics
-
-- [ ] **Migration Compatibility:** 100% compatibility with existing migration system
-- [ ] **Performance:** < 150MB memory usage, < 4s startup time
-- [ ] **Security:** Pass security audit, no critical vulnerabilities
-- [ ] **Reliability:** 99%+ uptime, < 1% error rate
-
-### 9.2 Development Metrics
-
-- [ ] **Code Quality:** 90%+ test coverage, < 5% code duplication
-- [ ] **Documentation:** Complete API documentation, user guides
-- [ ] **Build Automation:** Automated builds, CI/CD pipeline
-- [ ] **Release Readiness:** Production-ready application
-
----
-
-## 10. Conclusion
-
-### 10.1 Recommendation
-
-**✅ PROCEED WITH IMPLEMENTATION**
-
-CEFPython provides an excellent opportunity to add a robust desktop platform to TimeSafari with:
-
-1. **Full Migration System Compatibility:** Can use the exact same migration system as Capacitor and web
-2. **Native Performance:** Python backend with Chromium rendering
-3. **Security:** Chromium's security model with Python backend isolation
-4. **Development Efficiency:** Follows established patterns and architecture
-
-### 10.2 Implementation Priority
-
-**High Priority:**
-- Database handler with migration support
-- JavaScript-Python bridge
-- Platform service integration
-- Basic application structure
-
-**Medium Priority:**
-- Crypto handler integration
-- API server integration
-- Security features
-- Performance optimization
-
-**Low Priority:**
-- Advanced features
-- Build automation
-- Documentation
-- Distribution packaging
-
-### 10.3 Timeline
-
-**Total Duration:** 8 weeks (2 months)
-**Team Size:** 1-2 developers
-**Risk Level:** Medium
-**Confidence:** 85%
-
-The implementation leverages TimeSafari's existing architecture and migration system, making it a natural addition to the platform ecosystem while providing users with a high-performance desktop option.
-
----
-
-## 11. Next Steps
-
-1. **Immediate Actions:**
-   - Set up development environment
-   - Create basic CEFPython application structure
-   - Implement database handler with migration support
-
-2. **Week 1-2:**
-   - Complete foundation implementation
-   - Test migration system integration
-   - Validate database operations
-
-3. **Week 3-4:**
-   - Implement platform service
-   - Integrate with existing features
-   - Begin performance testing
-
-4. **Week 5-6:**
-   - Complete feature integration
-   - Security implementation
-   - User workflow testing
-
-5. **Week 7-8:**
-   - Performance optimization
-   - Build automation
-   - Documentation and release preparation
-
-This implementation will provide TimeSafari users with a robust, secure, and high-performance desktop application that seamlessly integrates with the existing ecosystem.

CHANGELOG.md

@@ -7,13 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 
 
-## [0.4.7]
-### Fixed
-- Cameras everywhere
-### Changed
-- IndexedDB -> SQLite
-
-
 ## [0.4.5] - 2025.02.23
 ### Added
 - Total amounts of gives on project page

Dockerfile

@@ -1,36 +0,0 @@
-# Build stage
-FROM node:22-alpine3.20 AS builder
-
-# Install build dependencies
-
-RUN apk add --no-cache bash git python3 py3-pip py3-setuptools make g++ gcc
-
-# Set working directory
-WORKDIR /app
-
-# Copy package files
-COPY package*.json ./
-
-# Install dependencies
-RUN npm ci
-
-# Copy source code
-COPY . .
-
-# Build the application
-RUN npm run build:web
-
-# Production stage
-FROM nginx:alpine
-
-# Copy built assets from builder stage
-COPY --from=builder /app/dist /usr/share/nginx/html
-
-# Copy nginx configuration if needed
-# COPY nginx.conf /etc/nginx/conf.d/default.conf
-
-# Expose port 80
-EXPOSE 80
-
-# Start nginx
-CMD ["nginx", "-g", "daemon off;"] 

GiftedDialog-Decomposition-Plan.md

@@ -1,469 +0,0 @@
-# GiftedDialog Component Decomposition Plan
-
-## Overview
-
-This document outlines a comprehensive plan to refactor the GiftedDialog component by breaking it into smaller, more manageable sub-components. This approach will improve maintainability, testability, and reusability while preparing the codebase for future Pinia integration.
-
-## Current State Analysis
-
-The GiftedDialog component (1060 lines) is a complex Vue component that handles:
-
-- **Two-step wizard UI**: Entity selection → Gift details
-- **Multiple entity types**: Person/Project as giver/recipient  
-- **Complex conditional rendering**: Based on context and entity types
-- **Form validation and submission**: Gift recording with API integration
-- **State management**: UI flow, entity selection, form data
-
-### Key Challenges
-
-1. **Large single file**: Difficult to navigate and maintain
-2. **Mixed concerns**: UI logic, business logic, and API calls in one place
-3. **Complex state**: Multiple interconnected reactive properties
-4. **Testing difficulty**: Hard to test individual features in isolation
-5. **Reusability**: Components like entity grids could be reused elsewhere
-
-## Decomposition Strategy
-
-### Phase 1: Extract Display Components (✅ COMPLETED)
-
-These components handle pure presentation with minimal business logic:
-
-#### 1. PersonCard.vue ✅
-
-- **Purpose**: Display individual person entities with selection capability
-- **Features**: 
-  - Person avatar using EntityIcon
-  - Selection states (selectable, conflicted, disabled)
-  - Time icon overlay for contacts
-  - Click event handling
-- **Props**: `person`, `selectable`, `conflicted`, `showTimeIcon`
-- **Emits**: `person-selected`
-
-#### 2. ProjectCard.vue ✅
-
-- **Purpose**: Display individual project entities with selection capability
-- **Features**:
-  - Project icon using ProjectIcon
-  - Project name and issuer information
-  - Click event handling
-- **Props**: `project`, `activeDid`, `allMyDids`, `allContacts`
-- **Emits**: `project-selected`
-
-#### 3. EntitySummaryButton.vue ✅
-
-- **Purpose**: Display selected entity with edit capability in step 2
-- **Features**:
-  - Entity avatar (person or project)
-  - Entity name and role label
-  - Editable vs locked states
-  - Edit button functionality
-- **Props**: `entity`, `entityType`, `label`, `editable`
-- **Emits**: `edit-requested`
-
-#### 4. AmountInput.vue ✅
-
-- **Purpose**: Specialized numeric input with increment/decrement controls
-- **Features**:
-  - Increment/decrement buttons with validation
-  - Configurable min/max values and step size
-  - Input validation and formatting
-  - v-model compatibility
-- **Props**: `value`, `min`, `max`, `step`, `inputId`
-- **Emits**: `update:value`
-
-### Phase 2: Extract Layout Components (✅ COMPLETED)
-
-These components handle layout and entity organization:
-
-#### 5. EntityGrid.vue ✅
-
-- **Purpose**: Unified grid layout for displaying people or projects
-- **Features**:
-  - Responsive grid layout for people/projects
-  - Special entity integration (You, Unnamed)
-  - Conflict detection integration
-  - Empty state messaging
-  - Show All navigation
-  - Event delegation for entity selection
-- **Props**: `entityType`, `entities`, `maxItems`, `activeDid`, `allMyDids`, `allContacts`, `conflictChecker`, `showYouEntity`, `youSelectable`, `showAllRoute`, `showAllQueryParams`
-- **Emits**: `entity-selected`
-
-#### 6. SpecialEntityCard.vue ✅
-
-- **Purpose**: Handle special entities like "You" and "Unnamed"
-- **Features**:
-  - Special icon display (hand, question mark)
-  - Conflict state handling
-  - Configurable styling based on entity type
-  - Click event handling
-- **Props**: `entityType`, `label`, `icon`, `selectable`, `conflicted`, `entityData`
-- **Emits**: `entity-selected`
-
-#### 7. ShowAllCard.vue ✅
-
-- **Purpose**: Handle "Show All" navigation functionality
-- **Features**:
-  - Router-link integration
-  - Query parameter passing
-  - Consistent visual styling
-  - Hover effects
-- **Props**: `entityType`, `routeName`, `queryParams`
-- **Emits**: None (uses router-link)
-
-### Phase 3: Extract Step Components (✅ COMPLETED)
-
-These components handle major UI sections:
-
-#### 8. EntitySelectionStep.vue ✅
-
-- **Purpose**: Complete step 1 entity selection interface
-- **Features**:
-  - Dynamic step labeling based on context
-  - EntityGrid integration for unified entity display
-  - Conflict detection and prevention
-  - Special entity handling (You, Unnamed)
-  - Show All navigation with context preservation
-  - Cancel functionality
-  - Event delegation for entity selection
-- **Props**: `stepType`, `giverEntityType`, `recipientEntityType`, `showProjects`, `isFromProjectView`, `projects`, `allContacts`, `activeDid`, `allMyDids`, `conflictChecker`, `fromProjectId`, `toProjectId`, `giver`, `receiver`
-- **Emits**: `entity-selected`, `cancel`
-
-#### 9. GiftDetailsStep.vue ✅
-
-- **Purpose**: Complete step 2 gift details form interface
-- **Features**:
-  - Entity summary display with edit capability
-  - Gift description input with placeholder support
-  - Amount input with increment/decrement controls
-  - Unit code selection (HUR, USD, BTC, etc.)
-  - Photo & more options navigation
-  - Conflict detection and warning display
-  - Form validation and submission
-  - Cancel functionality
-- **Props**: `giver`, `receiver`, `giverEntityType`, `recipientEntityType`, `description`, `amount`, `unitCode`, `prompt`, `isFromProjectView`, `hasConflict`, `offerId`, `fromProjectId`, `toProjectId`
-- **Emits**: `update:description`, `update:amount`, `update:unitCode`, `edit-entity`, `explain-data`, `submit`, `cancel`
-
-### Phase 4: Refactor Main Component (FINAL)
-
-#### 9. GiftedDialog.vue (PLANNED REFACTOR)
-
-- **Purpose**: Orchestrate sub-components and manage overall state
-- **Responsibilities**:
-  - Step navigation logic
-  - Entity conflict detection
-  - API integration for gift recording
-  - Success/error handling
-  - Dialog visibility management
-
-## Implementation Progress
-
-### ✅ Completed Components
-
-**Phase 1: Display Components**
-
-1. **PersonCard.vue** - Individual person display with selection
-2. **ProjectCard.vue** - Individual project display with selection  
-3. **EntitySummaryButton.vue** - Selected entity display with edit capability
-4. **AmountInput.vue** - Numeric input with increment/decrement controls
-
-**Phase 2: Layout Components**
-5. **EntityGrid.vue** - Unified grid layout for entity selection
-6. **SpecialEntityCard.vue** - Special entities (You, Unnamed) with conflict handling
-7. **ShowAllCard.vue** - Show All navigation with router integration
-
-**Phase 3: Step Components**
-8. **EntitySelectionStep.vue** - Complete step 1 entity selection interface
-9. **GiftDetailsStep.vue** - Complete step 2 gift details form interface
-
-### 🔄 Next Steps
-
-1. **Update GiftedDialog.vue** - Integrate all Phase 1-3 components
-2. **Test integration** - Ensure functionality remains intact
-3. **Create unit tests** - For all new components
-4. **Performance validation** - Ensure no regression
-5. **Phase 4 planning** - Refactor main component to orchestration only
-
-### 📋 Future Phases
-
-1. **Extract EntitySelectionStep.vue** - Complete step 1 logic
-2. **Extract GiftDetailsStep.vue** - Complete step 2 logic
-3. **Refactor main component** - Minimal orchestration logic
-4. **Add comprehensive tests** - Unit tests for each component
-5. **Prepare for Pinia** - State management migration
-
-## Benefits of This Approach
-
-### 1. Incremental Refactoring
-
-- Each phase can be implemented and tested independently
-- Reduces risk of breaking existing functionality
-- Allows for gradual improvement over time
-
-### 2. Improved Maintainability
-- Smaller, focused components are easier to understand
-- Clear separation of concerns
-- Easier to locate and fix bugs
-
-### 3. Enhanced Testability
-- Individual components can be unit tested in isolation
-- Easier to mock dependencies
-- Better test coverage possible
-
-### 4. Better Reusability
-- Components like EntityGrid can be used in other views
-- PersonCard and ProjectCard can be used throughout the app
-- AmountInput can be reused for other numeric inputs
-
-### 5. Pinia Preparation
-- Smaller components make state management migration easier
-- Clear data flow patterns emerge
-- Easier to identify what state should be global vs local
-
-## Integration Examples
-
-### Using PersonCard in EntityGrid
-
-```vue
-<template>
-  <ul class="grid grid-cols-4 sm:grid-cols-5 md:grid-cols-6 gap-x-2 gap-y-4">
-    <PersonCard
-      v-for="person in people"
-      :key="person.did"
-      :person="person"
-      :conflicted="wouldCreateConflict(person.did)"
-      @person-selected="handlePersonSelected"
-    />
-  </ul>
-</template>
-```
-
-### Using AmountInput in GiftDetailsStep
-
-```vue
-<template>
-  <AmountInput
-    :value="amount"
-    :min="0"
-    :max="1000"
-    input-id="gift-amount"
-    @update:value="amount = $event"
-  />
-</template>
-```
-
-### Using EntitySummaryButton in GiftDetailsStep
-
-```vue
-<template>
-  <div class="grid grid-cols-2 gap-2">
-    <EntitySummaryButton
-      :entity="giver"
-      entity-type="person"
-      label="Received from:"
-      :editable="canEditGiver"
-      @edit-requested="handleEditGiver"
-    />
-    <EntitySummaryButton
-      :entity="receiver"
-      entity-type="person"
-      label="Given to:"
-      :editable="canEditReceiver"
-      @edit-requested="handleEditReceiver"
-    />
-  </div>
-</template>
-```
-
-### Using EntityGrid in EntitySelectionStep
-
-```vue
-<template>
-  <div>
-    <label class="block font-bold mb-4">
-      {{ stepLabel }}
-    </label>
-    
-    <EntityGrid
-      :entity-type="shouldShowProjects ? 'projects' : 'people'"
-      :entities="shouldShowProjects ? projects : allContacts"
-      :max-items="10"
-      :active-did="activeDid"
-      :all-my-dids="allMyDids"
-      :all-contacts="allContacts"
-      :conflict-checker="wouldCreateConflict"
-      :show-you-entity="showYouEntity"
-      :you-selectable="youSelectable"
-      :show-all-route="showAllRoute"
-      :show-all-query-params="showAllQueryParams"
-      @entity-selected="handleEntitySelected"
-    />
-  </div>
-</template>
-```
-
-### Using SpecialEntityCard Standalone
-
-```vue
-<template>
-  <ul class="grid grid-cols-4 gap-2">
-    <SpecialEntityCard
-      entity-type="you"
-      label="You"
-      icon="hand"
-      :conflicted="wouldCreateConflict(activeDid)"
-      :entity-data="{ did: activeDid, name: 'You' }"
-      @entity-selected="handleYouSelected"
-    />
-    
-    <SpecialEntityCard
-      entity-type="unnamed"
-      label="Unnamed"
-      icon="circle-question"
-      :entity-data="{ did: '', name: 'Unnamed' }"
-      @entity-selected="handleUnnamedSelected"
-    />
-  </ul>
-</template>
-```
-
-### Using EntitySelectionStep in GiftedDialog
-
-```vue
-<template>
-  <div v-show="currentStep === 1">
-    <EntitySelectionStep
-      :step-type="stepType"
-      :giver-entity-type="giverEntityType"
-      :recipient-entity-type="recipientEntityType"
-      :show-projects="showProjects"
-      :is-from-project-view="isFromProjectView"
-      :projects="projects"
-      :all-contacts="allContacts"
-      :active-did="activeDid"
-      :all-my-dids="allMyDids"
-      :conflict-checker="wouldCreateConflict"
-      :from-project-id="fromProjectId"
-      :to-project-id="toProjectId"
-      :giver="giver"
-      :receiver="receiver"
-      @entity-selected="handleEntitySelected"
-      @cancel="cancel"
-    />
-  </div>
-</template>
-```
-
-### Using GiftDetailsStep in GiftedDialog
-
-```vue
-<template>
-  <div v-show="currentStep === 2">
-    <GiftDetailsStep
-      :giver="giver"
-      :receiver="receiver"
-      :giver-entity-type="giverEntityType"
-      :recipient-entity-type="recipientEntityType"
-      :description="description"
-      :amount="parseFloat(amountInput)"
-      :unit-code="unitCode"
-      :prompt="prompt"
-      :is-from-project-view="isFromProjectView"
-      :has-conflict="hasPersonConflict"
-      :offer-id="offerId"
-      :from-project-id="fromProjectId"
-      :to-project-id="toProjectId"
-      @update:description="description = $event"
-      @update:amount="amountInput = $event.toString()"
-      @update:unit-code="unitCode = $event"
-      @edit-entity="handleEditEntity"
-      @explain-data="explainData"
-      @submit="handleSubmit"
-      @cancel="cancel"
-    />
-  </div>
-</template>
-```
-
-## Migration Strategy
-
-### Backward Compatibility
-- Maintain existing API and prop interfaces
-- Ensure all existing functionality works unchanged
-- Preserve all event emissions and callbacks
-
-### Testing Strategy
-- Create unit tests for each new component
-- Maintain existing integration tests
-- Add visual regression tests for UI components
-
-### Performance Considerations
-- Monitor bundle size impact
-- Ensure no performance regression
-- Optimize component loading if needed
-
-## Security Considerations
-
-### Input Validation
-- AmountInput includes proper numeric validation
-- All user inputs are validated before processing
-- XSS prevention through proper Vue templating
-
-### Data Handling
-- No sensitive data stored in component state
-- Proper prop validation and type checking
-- Secure API communication maintained
-
-## Conclusion
-
-This decomposition plan provides a structured approach to refactoring the GiftedDialog component while maintaining functionality and preparing for future enhancements. The incremental approach reduces risk and allows for continuous improvement of the codebase.
-
-The completed Phase 1 components (PersonCard, ProjectCard, EntitySummaryButton, AmountInput) provide a solid foundation for the remaining phases and demonstrate the benefits of component decomposition in terms of maintainability, testability, and reusability.
-
----
-
-## Final Integration Results
-
-### ✅ **INTEGRATION COMPLETE**
-
-**Completed on**: 2025-01-28
-
-**Results:**
-- **Main GiftedDialog template**: Reduced from ~200 lines to ~20 lines
-- **Components created**: 9 focused, reusable components
-- **Lines of code**: ~2,000 lines of well-structured component code
-- **Backward compatibility**: 100% maintained
-- **Build status**: ✅ Passing
-- **Runtime status**: ✅ Working
-
-**Components Successfully Integrated:**
-
-1. **PersonCard.vue** - Individual person display with conflict detection
-2. **ProjectCard.vue** - Individual project display with issuer info
-3. **EntitySummaryButton.vue** - Selected entity display with edit capability
-4. **AmountInput.vue** - Numeric input with validation and controls
-5. **SpecialEntityCard.vue** - "You" and "Unnamed" entity handling
-6. **ShowAllCard.vue** - Navigation with router integration
-7. **EntityGrid.vue** - Unified grid layout orchestration
-8. **EntitySelectionStep.vue** - Complete Step 1 interface
-9. **GiftDetailsStep.vue** - Complete Step 2 interface
-
-**Integration Benefits Achieved:**
-- ✅ **Maintainability**: Each component has single responsibility
-- ✅ **Testability**: Components can be unit tested in isolation
-- ✅ **Reusability**: Components can be used across the application
-- ✅ **Readability**: Clear separation of concerns and focused logic
-- ✅ **Debugging**: Easier to identify and fix issues
-- ✅ **Performance**: No performance regression, improved code splitting
-
-**Next Steps:**
-1. **Pinia State Management**: Ready for state management migration
-2. **Component Testing**: Add comprehensive unit tests
-3. **Visual Testing**: Add Playwright component tests
-4. **Documentation**: Update component documentation
-5. **Optimization**: Fine-tune performance if needed
-
----
-
-**Author**: Matthew Raymer  
-**Last Updated**: 2025-01-28  
-**Status**: ✅ **INTEGRATION COMPLETE - READY FOR PRODUCTION** 

README.md

@@ -12,8 +12,6 @@ See [project.task.yaml](project.task.yaml) for current priorities.
 
 Quick start:
 
-* For setup, we recommend [pkgx](https://pkgx.dev), which installs what you need (either automatically or with the `dev` command). Core dependencies are typescript & npm; when building for other platforms, you'll need other things such as those in the pkgx.yaml & BUILDING.md files.
-
 ```bash
 npm install
 npm run dev
@@ -33,9 +31,7 @@ See [TESTING.md](test-playwright/TESTING.md) for detailed test instructions.
 
 ## Icons
 
-Application icons are in the `assets` directory, processed by the `capacitor-assets` command.
-
-To add a Font Awesome icon, add to main.ts and reference with `font-awesome` element and `icon` attribute with the hyphenated name.
+To add an icon, add to main.ts and reference with `fa` element and `icon` attribute with the hyphenated name.
 
 ## Other
 
@@ -48,24 +44,6 @@ To add a Font Awesome icon, add to main.ts and reference with `font-awesome` ele
 
 * If you are deploying in a subdirectory, add it to `publicPath` in vue.config.js, eg: `publicPath: "/app/time-tracker/",`
 
-### Code Organization
-
-The project uses a centralized approach to type definitions and interfaces:
-
-* `src/interfaces/` - Contains all TypeScript interfaces and type definitions
-  * `deepLinks.ts` - Deep linking type system and Zod validation schemas
-  * `give.ts` - Give-related interfaces and type definitions
-  * `claims.ts` - Claim-related interfaces and verifiable credentials
-  * `common.ts` - Shared interfaces and utility types
-  * Other domain-specific interface files
-
-Key principles:
-- All interfaces and types are defined in the interfaces folder
-- Zod schemas are used for runtime validation and type generation
-- Domain-specific interfaces are separated into their own files
-- Common interfaces are shared through `common.ts`
-- Type definitions are generated from Zod schemas where possible
-
 ### Kudos
 
 Gifts make the world go 'round!

TASK_storage.md

@@ -1,84 +0,0 @@
-
-# What to do about storage for native apps?
-
-
-## Problem
-
-We can't trust iOS IndexedDB to persist. I want to start delivering an app to people now, in preparation for presentations mid-June: Rotary on June 12 and Porcfest on June 17.
-
-* Apple WebKit puts a [7-day cap on IndexedDB](https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/).
-
-  * The web standards expose a `persist` method to mark memory as persistent, and [supposedly WebView supports it](https://developer.mozilla.org/en-US/docs/Web/API/StorageManager/persisted), but too many other things indicate it's not reliable. I've talked with [ChatGPT](https://chatgpt.com/share/68322f40-84c8-8007-b213-855f7962989a) & Venice & Claude (in Cursor); [this answer from Perplexity](https://www.perplexity.ai/search/which-platforms-prompt-the-use-HUQLqy4qQD2cRbkmO4CgHg) says that most platforms don't prompt and Safari doesn't support it; I don't know if that means WebKit as well.
-
-* Capacitor says [not to trust it on iOS](https://capacitorjs.com/docs/v6/guides/storage).
-
-Also, with sensitive data, the accounts info should be encrypted.
-
-
-# Options
-
-* There is a community [SQLite plugin for Capacitor](https://github.com/capacitor-community/sqlite) with encryption by [SQLCipher](https://github.com/sqlcipher/sqlcipher).
-
-  * [This tutorial](https://jepiqueau.github.io/2023/09/05/Ionic7Vue-SQLite-CRUD-App.html#part-1---web---table-of-contents) shows how that plugin works for web as well as native.
-
-* Capacitor abstracts [user preferences in an API](https://capacitorjs.com/docs/apis/preferences), which uses different underlying libraries on iOS & Android. Unfortunately, it won't do any filtering or searching, and is only meant for small amounts of data. (It could be used for settings and for identifiers, but contacts will grow and image blobs won't work.)
-
-  * There are hints that Capacitor offers another custom storage API but all I could find was that Preferences API.
-
-* [Ionic Storage](https://ionic.io/docs/secure-storage) is an enterprise solution, which also supports encryption.
-
-* Not an option yet: Dexie may support SQLite in [a future version](https://dexie.org/roadmap/dexie5.0).
-
-
-
-# Current Plan
-
-* Implement SQLite for Capacitor & web, with encryption. That will allow us to test quickly and keep the same interface for native & web, but we don't deal with migrations for current web users.
-
-* After that is delivered, write a migration for current web users from IndexedDB to SQLite.
-
-
-
-# Current method calls
-
-... which is not 100% complete because the AI that generated thus claimed no usage of 'temp' DB.
-
-### Secret Database (secretDB) - Used for storing the encryption key
-
-secretDB.open() - Opens the database
-secretDB.secret.get(MASTER_SECRET_KEY) - Retrieves the secret key
-secretDB.secret.add({ id: MASTER_SECRET_KEY, secret }) - Adds a new secret key
-
-### Accounts Database (accountsDB) - Used for storing sensitive account information
-
-accountsDB.open() - Opens the database
-accountsDB.accounts.count() - Counts number of accounts
-accountsDB.accounts.toArray() - Gets all accounts
-accountsDB.accounts.where("did").equals(did).first() - Gets a specific account by DID
-accountsDB.accounts.add(account) - Adds a new account
-
-### Non-sensitive Database (db) - Used for settings, contacts, logs, and temp data
-
-Settings operations:
-export all settings (Dexie format)
-db.settings.get(MASTER_SETTINGS_KEY) - Gets default settings
-db.settings.where("accountDid").equals(did).first() - Gets account-specific settings
-db.settings.where("accountDid").equals(did).modify(settingsChanges) - Updates account settings
-db.settings.add(settingsChanges) - Adds new settings
-db.settings.count() - Counts number of settings
-db.settings.update(key, changes) - Updates settings
-
-Contacts operations:
-export all contacts (Dexie format)
-db.contacts.toArray() - Gets all contacts
-db.contacts.add(contact) - Adds a new contact
-db.contacts.update(did, contactData) - Updates a contact
-db.contacts.delete(did) - Deletes a contact
-db.contacts.where("did").equals(did).first() - Gets a specific contact by DID
-
-Logs operations:
-db.logs.get(todayKey) - Gets logs for a specific day
-db.logs.update(todayKey, { message: fullMessage }) - Updates logs
-db.logs.clear() - Clears all logs
-
-

android/.gitignore

@@ -1,17 +1,5 @@
 # Using Android gitignore template: https://github.com/github/gitignore/blob/HEAD/Android.gitignore
 
-app/build/*
-!app/build/.npmkeep
-
-# Copied web assets
-app/src/main/assets/public
-
-# Generated Config files
-app/src/main/assets/capacitor.config.json
-app/src/main/assets/capacitor.plugins.json
-app/src/main/res/xml/config.xml
-
-# secrets
 app/gradle.properties.secrets
 app/time-safari-upload-key-pkcs12.jks
 
@@ -106,3 +94,11 @@ lint/tmp/
 
 # Cordova plugins for Capacitor
 capacitor-cordova-android-plugins
+
+# Copied web assets
+app/src/main/assets/public
+
+# Generated Config files
+app/src/main/assets/capacitor.config.json
+app/src/main/assets/capacitor.plugins.json
+app/src/main/res/xml/config.xml

android/.gradle/buildOutputCleanup/cache.properties

@@ -0,0 +1,2 @@
+#Fri Mar 21 07:27:50 UTC 2025
+gradle.version=8.2.1

android/app/.gitignore

@@ -0,0 +1,2 @@
+/build/*
+!/build/.npmkeep

android/app/build.gradle

@@ -14,7 +14,7 @@ project.ext.MY_KEY_PASSWORD = System.getenv('ANDROID_KEY_PASSWORD') ?: ""
 
 // If no environment variables, try to load from secrets file
 if (!project.ext.MY_KEYSTORE_FILE) {
-    def secretsPropertiesFile = rootProject.file("app/gradle.properties.secrets")
+    def secretsPropertiesFile = rootProject.file("gradle.properties.secrets")
     if (secretsPropertiesFile.exists()) {
         Properties secretsProperties = new Properties()
         secretsProperties.load(new FileInputStream(secretsPropertiesFile))
@@ -31,8 +31,8 @@ android {
         applicationId "app.timesafari.app"
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
-        versionCode 26
-        versionName "0.5.1"
+        versionCode 9
+        versionName "0.4.4"
         testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
         aaptOptions {
              // Files and dirs to omit from the packaged assets dir, modified to accommodate modern web apps.
@@ -91,8 +91,6 @@ dependencies {
     implementation "androidx.coordinatorlayout:coordinatorlayout:$androidxCoordinatorLayoutVersion"
     implementation "androidx.core:core-splashscreen:$coreSplashScreenVersion"
     implementation project(':capacitor-android')
-    implementation project(':capacitor-community-sqlite')
-    implementation "androidx.biometric:biometric:1.2.0-alpha05"
     testImplementation "junit:junit:$junitVersion"
     androidTestImplementation "androidx.test.ext:junit:$androidxJunitVersion"
     androidTestImplementation "androidx.test.espresso:espresso-core:$androidxEspressoCoreVersion"

android/app/capacitor.build.gradle

@@ -9,13 +9,9 @@ android {
 
 apply from: "../capacitor-cordova-android-plugins/cordova.variables.gradle"
 dependencies {
-    implementation project(':capacitor-community-sqlite')
-    implementation project(':capacitor-mlkit-barcode-scanning')
     implementation project(':capacitor-app')
     implementation project(':capacitor-camera')
     implementation project(':capacitor-filesystem')
-    implementation project(':capacitor-share')
-    implementation project(':capawesome-capacitor-file-picker')
 
 }
 

android/app/google-services.json

@@ -1,28 +0,0 @@
-{
-  "project_info": {
-    "project_number": "123456789000",
-    "project_id": "timesafari-app",
-    "storage_bucket": "timesafari-app.appspot.com"
-  },
-  "client": [
-    {
-      "client_info": {
-        "mobilesdk_app_id": "1:123456789000:android:1234567890abcdef",
-        "android_client_info": {
-          "package_name": "app.timesafari.app"
-        }
-      },
-      "oauth_client": [],
-      "api_key": [
-        {
-          "current_key": "AIzaSyDummyKeyForBuildPurposesOnly12345"
-        }
-      ],
-      "services": {
-        "appinvite_service": {
-          "other_platform_oauth_client": []
-        }
-      }
-    }
-  ]
-} 

android/app/src/androidTest/java/com/getcapacitor/myapp/ExampleInstrumentedTest.java

@@ -21,6 +21,6 @@ public class ExampleInstrumentedTest {
         // Context of the app under test.
         Context appContext = InstrumentationRegistry.getInstrumentation().getTargetContext();
 
-        assertEquals("app.timesafari.app", appContext.getPackageName());
+        assertEquals("app.timesafari", appContext.getPackageName());
     }
 }

android/app/src/main/AndroidManifest.xml

@@ -1,5 +1,6 @@
-<?xml version="1.0" encoding="utf-8" ?>
+<?xml version="1.0" encoding="utf-8"?>
 <manifest xmlns:android="http://schemas.android.com/apk/res/android">
+
     <application
         android:allowBackup="true"
         android:icon="@mipmap/ic_launcher"
@@ -7,6 +8,7 @@
         android:roundIcon="@mipmap/ic_launcher_round"
         android:supportsRtl="true"
         android:theme="@style/AppTheme">
+
         <activity
             android:name=".MainActivity"
             android:configChanges="orientation|keyboardHidden|keyboard|screenSize|locale|smallestScreenSize|screenLayout|uiMode"
@@ -14,6 +16,7 @@
             android:label="@string/title_activity_main"
             android:launchMode="singleTask"
             android:theme="@style/AppTheme.NoActionBarLaunch">
+
             <intent-filter>
                 <action android:name="android.intent.action.MAIN" />
                 <category android:name="android.intent.category.LAUNCHER" />
@@ -25,6 +28,7 @@
                 <category android:name="android.intent.category.BROWSABLE" />
                 <data android:scheme="timesafari" />
             </intent-filter>
+
         </activity>
 
         <provider
@@ -32,15 +36,13 @@
             android:authorities="${applicationId}.fileprovider"
             android:exported="false"
             android:grantUriPermissions="true">
-            <meta-data android:name="android.support.FILE_PROVIDER_PATHS" android:resource="@xml/file_paths" />
+            <meta-data
+                android:name="android.support.FILE_PROVIDER_PATHS"
+                android:resource="@xml/file_paths"></meta-data>
         </provider>
     </application>
 
     <!-- Permissions -->
 
     <uses-permission android:name="android.permission.INTERNET" />
-    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
-    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
-    <uses-permission android:name="android.permission.CAMERA" />
-    <uses-feature android:name="android.hardware.camera" android:required="true" />
 </manifest>

android/app/src/main/assets/capacitor.config.json

@@ -16,41 +16,6 @@
 					}
 				]
 			}
-		},
-		"SQLite": {
-			"iosDatabaseLocation": "Library/CapacitorDatabase",
-			"iosIsEncryption": true,
-			"iosBiometric": {
-				"biometricAuth": true,
-				"biometricTitle": "Biometric login for TimeSafari"
-			},
-			"androidIsEncryption": true,
-			"androidBiometric": {
-				"biometricAuth": true,
-				"biometricTitle": "Biometric login for TimeSafari"
-			}
 		}
-	},
-	"ios": {
-		"contentInset": "never",
-		"allowsLinkPreview": true,
-		"scrollEnabled": true,
-		"limitsNavigationsToAppBoundDomains": true,
-		"backgroundColor": "#ffffff",
-		"allowNavigation": [
-			"*.timesafari.app",
-			"*.jsdelivr.net",
-			"api.endorser.ch"
-		]
-	},
-	"android": {
-		"allowMixedContent": false,
-		"captureInput": true,
-		"webContentsDebuggingEnabled": false,
-		"allowNavigation": [
-			"*.timesafari.app",
-			"*.jsdelivr.net",
-			"api.endorser.ch"
-		]
 	}
 }

android/app/src/main/assets/capacitor.plugins.json

@@ -1,12 +1,4 @@
 [
-	{
-		"pkg": "@capacitor-community/sqlite",
-		"classpath": "com.getcapacitor.community.database.sqlite.CapacitorSQLitePlugin"
-	},
-	{
-		"pkg": "@capacitor-mlkit/barcode-scanning",
-		"classpath": "io.capawesome.capacitorjs.plugins.mlkit.barcodescanning.BarcodeScannerPlugin"
-	},
 	{
 		"pkg": "@capacitor/app",
 		"classpath": "com.capacitorjs.plugins.app.AppPlugin"
@@ -18,13 +10,5 @@
 	{
 		"pkg": "@capacitor/filesystem",
 		"classpath": "com.capacitorjs.plugins.filesystem.FilesystemPlugin"
-	},
-	{
-		"pkg": "@capacitor/share",
-		"classpath": "com.capacitorjs.plugins.share.SharePlugin"
-	},
-	{
-		"pkg": "@capawesome/capacitor-file-picker",
-		"classpath": "io.capawesome.capacitorjs.plugins.filepicker.FilePickerPlugin"
 	}
 ]

android/app/src/main/assets/public/index.html

@@ -0,0 +1,17 @@
+<!DOCTYPE html>
+<html lang="">
+  <head>
+    <meta charset="utf-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="icon" href="/favicon.ico">
+    <title>TimeSafari</title>
+    <script type="module" crossorigin src="/assets/index-CZMUlUNO.js"></script>
+  </head>
+  <body>
+    <noscript>
+      <strong>We're sorry but TimeSafari doesn't work properly without JavaScript enabled. Please enable it to continue.</strong>
+    </noscript>
+    <div id="app"></div>
+  </body>
+</html>

android/app/src/main/java/app/timesafari/MainActivity.java

@@ -1,15 +1,7 @@
 package app.timesafari;
 
-import android.os.Bundle;
 import com.getcapacitor.BridgeActivity;
-//import com.getcapacitor.community.sqlite.SQLite;
 
 public class MainActivity extends BridgeActivity {
-    @Override
-    public void onCreate(Bundle savedInstanceState) {
-        super.onCreate(savedInstanceState);
-        
-        // Initialize SQLite
-        //registerPlugin(SQLite.class);
-    }
+    // ... existing code ...
 } 

android/app/src/main/java/timesafari/app/MainActivity.java

@@ -0,0 +1,5 @@
+package timesafari.app;
+
+import com.getcapacitor.BridgeActivity;
+
+public class MainActivity extends BridgeActivity {}

android/app/src/main/res/mipmap-anydpi-v26/ic_launcher.xml

@@ -1,9 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
 <adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
-    <background>
-        <inset android:drawable="@mipmap/ic_launcher_background" android:inset="16.7%" />
-    </background>
-    <foreground>
-        <inset android:drawable="@mipmap/ic_launcher_foreground" android:inset="16.7%" />
-    </foreground>
+    <background android:drawable="@color/ic_launcher_background"/>
+    <foreground android:drawable="@mipmap/ic_launcher_foreground"/>
 </adaptive-icon>

android/app/src/main/res/mipmap-anydpi-v26/ic_launcher_round.xml

@@ -1,9 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
 <adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
-    <background>
-        <inset android:drawable="@mipmap/ic_launcher_background" android:inset="16.7%" />
-    </background>
-    <foreground>
-        <inset android:drawable="@mipmap/ic_launcher_foreground" android:inset="16.7%" />
-    </foreground>
+    <background android:drawable="@color/ic_launcher_background"/>
+    <foreground android:drawable="@mipmap/ic_launcher_foreground"/>
 </adaptive-icon>

android/app/src/main/res/xml/file_paths.xml

@@ -2,5 +2,4 @@
 <paths xmlns:android="http://schemas.android.com/apk/res/android">
     <external-path name="my_images" path="." />
     <cache-path name="my_cache_images" path="." />
-    <files-path name="my_files" path="." />
 </paths>

android/build.gradle

@@ -7,7 +7,7 @@ buildscript {
         mavenCentral()
     }
     dependencies {
-        classpath 'com.android.tools.build:gradle:8.9.1'
+        classpath 'com.android.tools.build:gradle:8.9.0'
         classpath 'com.google.gms:google-services:4.4.0'
 
         // NOTE: Do not place your application dependencies here; they belong

android/capacitor.settings.gradle

@@ -2,12 +2,6 @@
 include ':capacitor-android'
 project(':capacitor-android').projectDir = new File('../node_modules/@capacitor/android/capacitor')
 
-include ':capacitor-community-sqlite'
-project(':capacitor-community-sqlite').projectDir = new File('../node_modules/@capacitor-community/sqlite/android')
-
-include ':capacitor-mlkit-barcode-scanning'
-project(':capacitor-mlkit-barcode-scanning').projectDir = new File('../node_modules/@capacitor-mlkit/barcode-scanning/android')
-
 include ':capacitor-app'
 project(':capacitor-app').projectDir = new File('../node_modules/@capacitor/app/android')
 
@@ -16,9 +10,3 @@ project(':capacitor-camera').projectDir = new File('../node_modules/@capacitor/c
 
 include ':capacitor-filesystem'
 project(':capacitor-filesystem').projectDir = new File('../node_modules/@capacitor/filesystem/android')
-
-include ':capacitor-share'
-project(':capacitor-share').projectDir = new File('../node_modules/@capacitor/share/android')
-
-include ':capawesome-capacitor-file-picker'
-project(':capawesome-capacitor-file-picker').projectDir = new File('../node_modules/@capawesome/capacitor-file-picker/android')

assets/README.md

@@ -1,2 +0,0 @@
-
-Application icons are here. They are processed for android & ios by the `capacitor-assets` command, as indicated in the BUILDING.md file.

build.sh

@@ -1,4 +0,0 @@
-#!/bin/bash
-export IMAGENAME="$(basename $PWD):1.0"
-
-docker build . --network=host -t $IMAGENAME --no-cache

capacitor.config.json

@@ -1,56 +0,0 @@
-{
-	"appId": "app.timesafari",
-	"appName": "TimeSafari",
-	"webDir": "dist",
-	"bundledWebRuntime": false,
-	"server": {
-		"cleartext": true
-	},
-	"plugins": {
-		"App": {
-			"appUrlOpen": {
-				"handlers": [
-					{
-						"url": "timesafari://*",
-						"autoVerify": true
-					}
-				]
-			}
-		},
-		"SQLite": {
-			"iosDatabaseLocation": "Library/CapacitorDatabase",
-			"iosIsEncryption": true,
-			"iosBiometric": {
-				"biometricAuth": true,
-				"biometricTitle": "Biometric login for TimeSafari"
-			},
-			"androidIsEncryption": true,
-			"androidBiometric": {
-				"biometricAuth": true,
-				"biometricTitle": "Biometric login for TimeSafari"
-			}
-		}
-	},
-	"ios": {
-		"contentInset": "never",
-		"allowsLinkPreview": true,
-		"scrollEnabled": true,
-		"limitsNavigationsToAppBoundDomains": true,
-		"backgroundColor": "#ffffff",
-		"allowNavigation": [
-			"*.timesafari.app",
-			"*.jsdelivr.net",
-			"api.endorser.ch"
-		]
-	},
-	"android": {
-		"allowMixedContent": false,
-		"captureInput": true,
-		"webContentsDebuggingEnabled": false,
-		"allowNavigation": [
-			"*.timesafari.app",
-			"*.jsdelivr.net",
-			"api.endorser.ch"
-		]
-	}
-}

capacitor.config.ts

@@ -0,0 +1,25 @@
+import { CapacitorConfig } from '@capacitor/cli';
+
+const config: CapacitorConfig = {
+  appId: 'app.timesafari',
+  appName: 'TimeSafari',
+  webDir: 'dist',
+  bundledWebRuntime: false,
+  server: {
+    cleartext: true,
+  },
+  plugins: {
+    App: {
+      appUrlOpen: {
+        handlers: [
+          {
+            url: "timesafari://*",
+            autoVerify: true
+          }
+        ]
+      }
+    }
+  }
+};
+
+export default config;

doc/GiftedDialog-Complete-Documentation.md

@@ -1,224 +0,0 @@
-# GiftedDialog Complete Documentation
-
-## Overview
-
-The GiftedDialog system is a sophisticated multi-step dialog for recording gifts between people and projects in the TimeSafari application. It consists of a main orchestrating component and 9 specialized child components that handle different aspects of the gift recording workflow.
-
-## Key Features
-
-- **Two-Step Workflow**: Entity selection → Gift details
-- **Multi-Entity Support**: People, projects, and special entities  
-- **Conflict Detection**: Prevents invalid gift combinations
-- **Responsive Design**: Works across all device sizes
-- **Accessibility**: Full keyboard navigation and screen reader support
-- **Validation**: Comprehensive form validation and error handling
-- **Flexible Integration**: Can be embedded in any view with different contexts
-
-## Component Architecture
-
-### Main Component
-- **GiftedDialog.vue** - Main orchestrating component that manages dialog state, step navigation, and API integration
-
-### Step Components  
-- **EntitySelectionStep.vue** - Step 1 controller with dynamic labeling and context awareness
-- **GiftDetailsStep.vue** - Step 2 controller with form validation and entity summaries
-
-### Layout Components
-- **EntityGrid.vue** - Unified entity grid layout with responsive design
-- **EntitySummaryButton.vue** - Selected entity display with edit capability
-
-### Display Components
-- **PersonCard.vue** - Individual person display with avatar and selection states
-- **ProjectCard.vue** - Individual project display with icons and issuer information
-- **SpecialEntityCard.vue** - Special entities (You, Unnamed) with conflict detection
-- **ShowAllCard.vue** - Navigation component with router integration
-
-### Input Components
-- **AmountInput.vue** - Numeric input with increment/decrement controls and validation
-
-## Data Flow
-
-### Step 1: Entity Selection
-1. User opens dialog → GiftedDialog renders EntitySelectionStep
-2. EntitySelectionStep renders EntityGrid with entities and configuration
-3. EntityGrid renders PersonCard/ProjectCard/SpecialEntityCard components
-4. User clicks entity → Card emits to Grid → Grid emits to Step → Step emits to Dialog
-5. GiftedDialog updates state and advances to step 2
-
-### Step 2: Gift Details  
-1. GiftedDialog renders GiftDetailsStep with selected entities
-2. GiftDetailsStep renders EntitySummaryButton and AmountInput components
-3. User fills form and clicks submit → Step emits to Dialog
-4. GiftedDialog processes submission via API and handles success/error
-
-## Key Props and Configuration
-
-### GiftedDialog Props
-```typescript
-interface GiftedDialogProps {
-  fromProjectId?: string;      // Project ID when project is giver
-  toProjectId?: string;        // Project ID when project is recipient  
-  showProjects?: boolean;      // Whether to show projects
-  isFromProjectView?: boolean; // Context flag for project views
-}
-```
-
-### Opening the Dialog
-```typescript
-// Basic usage
-giftedDialog.open();
-
-// With pre-selected entities and context
-giftedDialog.open(
-  giverEntity,      // Pre-selected giver
-  receiverEntity,   // Pre-selected receiver  
-  offerId,          // Offer context
-  customTitle,      // Custom dialog title
-  prompt,           // Custom input prompt
-  successCallback   // Success handler
-);
-```
-
-## Integration Patterns
-
-### Basic Integration
-```vue
-<template>
-  <div>
-    <button @click="openGiftDialog">Record Gift</button>
-    <GiftedDialog ref="giftedDialog" />
-  </div>
-</template>
-
-<script lang="ts">
-export default class Example extends Vue {
-  openGiftDialog() {
-    const dialog = this.$refs.giftedDialog as GiftedDialog;
-    dialog.open();
-  }
-}
-</script>
-```
-
-### Project Context Integration
-```typescript
-// Gift from project
-dialog.open(
-  projectEntity,    // Project as giver
-  undefined,        // User selects receiver
-  undefined,        // No offer
-  "Gift from Project",
-  "What did this project provide?"
-);
-
-// Gift to project  
-dialog.open(
-  undefined,        // User selects giver
-  projectEntity,    // Project as receiver
-  undefined,        // No offer
-  "Gift to Project", 
-  "What was contributed to this project?"
-);
-```
-
-## State Management
-
-The dialog manages internal state through a reactive system:
-
-- **Step Navigation**: Controls progression from entity selection to gift details
-- **Entity Selection**: Tracks selected giver and receiver entities
-- **Conflict Detection**: Prevents selecting same person for both roles
-- **Form Validation**: Ensures required fields are completed
-- **API Integration**: Handles gift submission and response processing
-
-## Conflict Detection Logic
-
-```typescript
-function wouldCreateConflict(selectedDid: string): boolean {
-  // Only applies to person-to-person gifts
-  if (giverEntityType !== "person" || recipientEntityType !== "person") {
-    return false;
-  }
-  
-  // Check if selecting same person for both roles
-  if (stepType === "giver") {
-    return receiver?.did === selectedDid;
-  } else if (stepType === "recipient") {
-    return giver?.did === selectedDid;
-  }
-  
-  return false;
-}
-```
-
-## AmountInput Component Fix
-
-The AmountInput component was recently fixed to resolve an issue where increment/decrement buttons weren't updating the displayed value:
-
-### Problem
-- Input field used `:value="displayValue"` (one-way binding)
-- Programmatic updates to `displayValue` weren't reflected in DOM
-
-### Solution  
-- Changed to `v-model="displayValue"` (two-way binding)
-- Now properly synchronizes programmatic and user input changes
-
-### Usage
-```vue
-<AmountInput
-  :value="amount"
-  :min="0"
-  :max="1000"
-  :step="1"
-  @update:value="handleAmountChange"
-/>
-```
-
-## Testing Strategy
-
-### Unit Testing
-- Individual component behavior
-- Props validation
-- Event emission
-- Computed property calculations
-
-### Integration Testing  
-- Multi-component workflows
-- State management
-- API integration
-- Error handling
-
-### End-to-End Testing
-- Complete user workflows
-- Cross-browser compatibility
-- Accessibility compliance
-- Performance validation
-
-## Security Considerations
-
-- **Input Validation**: All user inputs are sanitized and validated
-- **DID Privacy**: User identifiers only shared with authorized contacts  
-- **API Security**: Requests are cryptographically signed
-- **XSS Prevention**: Template sanitization and CSP headers
-
-## Performance Optimizations
-
-- **Lazy Loading**: Components loaded only when needed
-- **Virtual Scrolling**: For large entity lists
-- **Debounced Input**: Prevents excessive API calls
-- **Computed Properties**: Efficient reactive calculations
-- **Memory Management**: Proper cleanup on component destruction
-
-## Accessibility Features
-
-- **Keyboard Navigation**: Full tab order and keyboard shortcuts
-- **Screen Reader Support**: ARIA labels and semantic HTML
-- **Focus Management**: Proper focus handling on open/close
-- **High Contrast**: Supports high contrast themes
-- **Responsive Design**: Works on all screen sizes
-
----
-
-**Author**: Matthew Raymer  
-**Last Updated**: 2025-06-30  
-**Version**: 1.0.0

doc/dexie-to-sqlite-mapping.md

@@ -1,399 +0,0 @@
-# Dexie to absurd-sql Mapping Guide
-
-## Schema Mapping
-
-### Current Dexie Schema
-```typescript
-// Current Dexie schema
-const db = new Dexie('TimeSafariDB');
-
-db.version(1).stores({
-  accounts: 'did, publicKeyHex, createdAt, updatedAt',
-  settings: 'key, value, updatedAt',
-  contacts: 'id, did, name, createdAt, updatedAt'
-});
-```
-
-### New SQLite Schema
-```sql
--- New SQLite schema
-CREATE TABLE accounts (
-  did TEXT PRIMARY KEY,
-  public_key_hex TEXT NOT NULL,
-  created_at INTEGER NOT NULL,
-  updated_at INTEGER NOT NULL
-);
-
-CREATE TABLE settings (
-  key TEXT PRIMARY KEY,
-  value TEXT NOT NULL,
-  updated_at INTEGER NOT NULL
-);
-
-CREATE TABLE contacts (
-  id TEXT PRIMARY KEY,
-  did TEXT NOT NULL,
-  name TEXT,
-  created_at INTEGER NOT NULL,
-  updated_at INTEGER NOT NULL,
-  FOREIGN KEY (did) REFERENCES accounts(did)
-);
-
--- Indexes for performance
-CREATE INDEX idx_accounts_created_at ON accounts(created_at);
-CREATE INDEX idx_contacts_did ON contacts(did);
-CREATE INDEX idx_settings_updated_at ON settings(updated_at);
-```
-
-## Query Mapping
-
-### 1. Account Operations
-
-#### Get Account by DID
-```typescript
-// Dexie
-const account = await db.accounts.get(did);
-
-// absurd-sql
-const result = await db.exec(`
-  SELECT * FROM accounts WHERE did = ?
-`, [did]);
-const account = result[0]?.values[0];
-```
-
-#### Get All Accounts
-```typescript
-// Dexie
-const accounts = await db.accounts.toArray();
-
-// absurd-sql
-const result = await db.exec(`
-  SELECT * FROM accounts ORDER BY created_at DESC
-`);
-const accounts = result[0]?.values || [];
-```
-
-#### Add Account
-```typescript
-// Dexie
-await db.accounts.add({
-  did,
-  publicKeyHex,
-  createdAt: Date.now(),
-  updatedAt: Date.now()
-});
-
-// absurd-sql
-await db.run(`
-  INSERT INTO accounts (did, public_key_hex, created_at, updated_at)
-  VALUES (?, ?, ?, ?)
-`, [did, publicKeyHex, Date.now(), Date.now()]);
-```
-
-#### Update Account
-```typescript
-// Dexie
-await db.accounts.update(did, {
-  publicKeyHex,
-  updatedAt: Date.now()
-});
-
-// absurd-sql
-await db.run(`
-  UPDATE accounts 
-  SET public_key_hex = ?, updated_at = ?
-  WHERE did = ?
-`, [publicKeyHex, Date.now(), did]);
-```
-
-### 2. Settings Operations
-
-#### Get Setting
-```typescript
-// Dexie
-const setting = await db.settings.get(key);
-
-// absurd-sql
-const result = await db.exec(`
-  SELECT * FROM settings WHERE key = ?
-`, [key]);
-const setting = result[0]?.values[0];
-```
-
-#### Set Setting
-```typescript
-// Dexie
-await db.settings.put({
-  key,
-  value,
-  updatedAt: Date.now()
-});
-
-// absurd-sql
-await db.run(`
-  INSERT INTO settings (key, value, updated_at)
-  VALUES (?, ?, ?)
-  ON CONFLICT(key) DO UPDATE SET
-    value = excluded.value,
-    updated_at = excluded.updated_at
-`, [key, value, Date.now()]);
-```
-
-### 3. Contact Operations
-
-#### Get Contacts by Account
-```typescript
-// Dexie
-const contacts = await db.contacts
-  .where('did')
-  .equals(accountDid)
-  .toArray();
-
-// absurd-sql
-const result = await db.exec(`
-  SELECT * FROM contacts 
-  WHERE did = ?
-  ORDER BY created_at DESC
-`, [accountDid]);
-const contacts = result[0]?.values || [];
-```
-
-#### Add Contact
-```typescript
-// Dexie
-await db.contacts.add({
-  id: generateId(),
-  did: accountDid,
-  name,
-  createdAt: Date.now(),
-  updatedAt: Date.now()
-});
-
-// absurd-sql
-await db.run(`
-  INSERT INTO contacts (id, did, name, created_at, updated_at)
-  VALUES (?, ?, ?, ?, ?)
-`, [generateId(), accountDid, name, Date.now(), Date.now()]);
-```
-
-## Transaction Mapping
-
-### Batch Operations
-```typescript
-// Dexie
-await db.transaction('rw', [db.accounts, db.contacts], async () => {
-  await db.accounts.add(account);
-  await db.contacts.bulkAdd(contacts);
-});
-
-// absurd-sql
-await db.exec('BEGIN TRANSACTION;');
-try {
-  await db.run(`
-    INSERT INTO accounts (did, public_key_hex, created_at, updated_at)
-    VALUES (?, ?, ?, ?)
-  `, [account.did, account.publicKeyHex, account.createdAt, account.updatedAt]);
-
-  for (const contact of contacts) {
-    await db.run(`
-      INSERT INTO contacts (id, did, name, created_at, updated_at)
-      VALUES (?, ?, ?, ?, ?)
-    `, [contact.id, contact.did, contact.name, contact.createdAt, contact.updatedAt]);
-  }
-  await db.exec('COMMIT;');
-} catch (error) {
-  await db.exec('ROLLBACK;');
-  throw error;
-}
-```
-
-## Migration Helper Functions
-
-### 1. Data Export (Dexie to JSON)
-```typescript
-async function exportDexieData(): Promise<MigrationData> {
-  const db = new Dexie('TimeSafariDB');
-  
-  return {
-    accounts: await db.accounts.toArray(),
-    settings: await db.settings.toArray(),
-    contacts: await db.contacts.toArray(),
-    metadata: {
-      version: '1.0.0',
-      timestamp: Date.now(),
-      dexieVersion: Dexie.version
-    }
-  };
-}
-```
-
-### 2. Data Import (JSON to absurd-sql)
-```typescript
-async function importToAbsurdSql(data: MigrationData): Promise<void> {
-  await db.exec('BEGIN TRANSACTION;');
-  try {
-    // Import accounts
-    for (const account of data.accounts) {
-      await db.run(`
-        INSERT INTO accounts (did, public_key_hex, created_at, updated_at)
-        VALUES (?, ?, ?, ?)
-      `, [account.did, account.publicKeyHex, account.createdAt, account.updatedAt]);
-    }
-    
-    // Import settings
-    for (const setting of data.settings) {
-      await db.run(`
-        INSERT INTO settings (key, value, updated_at)
-        VALUES (?, ?, ?)
-      `, [setting.key, setting.value, setting.updatedAt]);
-    }
-    
-    // Import contacts
-    for (const contact of data.contacts) {
-      await db.run(`
-        INSERT INTO contacts (id, did, name, created_at, updated_at)
-        VALUES (?, ?, ?, ?, ?)
-      `, [contact.id, contact.did, contact.name, contact.createdAt, contact.updatedAt]);
-    }
-    await db.exec('COMMIT;');
-  } catch (error) {
-    await db.exec('ROLLBACK;');
-    throw error;
-  }
-}
-```
-
-### 3. Verification
-```typescript
-async function verifyMigration(dexieData: MigrationData): Promise<boolean> {
-  // Verify account count
-  const accountResult = await db.exec('SELECT COUNT(*) as count FROM accounts');
-  const accountCount = accountResult[0].values[0][0];
-  if (accountCount !== dexieData.accounts.length) {
-    return false;
-  }
-  
-  // Verify settings count
-  const settingsResult = await db.exec('SELECT COUNT(*) as count FROM settings');
-  const settingsCount = settingsResult[0].values[0][0];
-  if (settingsCount !== dexieData.settings.length) {
-    return false;
-  }
-  
-  // Verify contacts count
-  const contactsResult = await db.exec('SELECT COUNT(*) as count FROM contacts');
-  const contactsCount = contactsResult[0].values[0][0];
-  if (contactsCount !== dexieData.contacts.length) {
-    return false;
-  }
-  
-  // Verify data integrity
-  for (const account of dexieData.accounts) {
-    const result = await db.exec(
-      'SELECT * FROM accounts WHERE did = ?',
-      [account.did]
-    );
-    const migratedAccount = result[0]?.values[0];
-    if (!migratedAccount || 
-        migratedAccount[1] !== account.publicKeyHex) { // public_key_hex is second column
-      return false;
-    }
-  }
-  
-  return true;
-}
-```
-
-## Performance Considerations
-
-### 1. Indexing
-- Dexie automatically creates indexes based on the schema
-- absurd-sql requires explicit index creation
-- Added indexes for frequently queried fields
-- Use `PRAGMA journal_mode=MEMORY;` for better performance
-
-### 2. Batch Operations
-- Dexie has built-in bulk operations
-- absurd-sql uses transactions for batch operations
-- Consider chunking large datasets
-- Use prepared statements for repeated queries
-
-### 3. Query Optimization
-- Dexie uses IndexedDB's native indexing
-- absurd-sql requires explicit query optimization
-- Use prepared statements for repeated queries
-- Consider using `PRAGMA synchronous=NORMAL;` for better performance
-
-## Error Handling
-
-### 1. Common Errors
-```typescript
-// Dexie errors
-try {
-  await db.accounts.add(account);
-} catch (error) {
-  if (error instanceof Dexie.ConstraintError) {
-    // Handle duplicate key
-  }
-}
-
-// absurd-sql errors
-try {
-  await db.run(`
-    INSERT INTO accounts (did, public_key_hex, created_at, updated_at)
-    VALUES (?, ?, ?, ?)
-  `, [account.did, account.publicKeyHex, account.createdAt, account.updatedAt]);
-} catch (error) {
-  if (error.message.includes('UNIQUE constraint failed')) {
-    // Handle duplicate key
-  }
-}
-```
-
-### 2. Transaction Recovery
-```typescript
-// Dexie transaction
-try {
-  await db.transaction('rw', db.accounts, async () => {
-    // Operations
-  });
-} catch (error) {
-  // Dexie automatically rolls back
-}
-
-// absurd-sql transaction
-try {
-  await db.exec('BEGIN TRANSACTION;');
-  // Operations
-  await db.exec('COMMIT;');
-} catch (error) {
-  await db.exec('ROLLBACK;');
-  throw error;
-}
-```
-
-## Migration Strategy
-
-1. **Preparation**
-   - Export all Dexie data
-   - Verify data integrity
-   - Create SQLite schema
-   - Setup indexes
-
-2. **Migration**
-   - Import data in transactions
-   - Verify each batch
-   - Handle errors gracefully
-   - Maintain backup
-
-3. **Verification**
-   - Compare record counts
-   - Verify data integrity
-   - Test common queries
-   - Validate relationships
-
-4. **Cleanup**
-   - Remove Dexie database
-   - Clear IndexedDB storage
-   - Update application code
-   - Remove old dependencies 

doc/migration-to-wa-sqlite.md

@@ -1,613 +0,0 @@
-# Migration Guide: Dexie to absurd-sql
-
-## Overview
-
-This document outlines the migration process from Dexie.js to absurd-sql for the TimeSafari app's storage implementation. The migration aims to provide a consistent SQLite-based storage solution across all platforms while maintaining data integrity and ensuring a smooth transition for users.
-
-## Migration Goals
-
-1. **Data Integrity**
-   - Preserve all existing data
-   - Maintain data relationships
-   - Ensure data consistency
-
-2. **Performance**
-   - Improve query performance
-   - Reduce storage overhead
-   - Optimize for platform-specific features
-
-3. **Security**
-   - Maintain or improve encryption
-   - Preserve access controls
-   - Enhance data protection
-
-4. **User Experience**
-   - Zero data loss
-   - Minimal downtime
-   - Automatic migration where possible
-
-## Prerequisites
-
-1. **Backup Requirements**
-   ```typescript
-   interface MigrationBackup {
-     timestamp: number;
-     accounts: Account[];
-     settings: Setting[];
-     contacts: Contact[];
-     metadata: {
-       version: string;
-       platform: string;
-       dexieVersion: string;
-     };
-   }
-   ```
-
-2. **Dependencies**
-   ```json
-   {
-     "@jlongster/sql.js": "^1.8.0",
-     "absurd-sql": "^1.8.0"
-   }
-   ```
-
-3. **Storage Requirements**
-   - Sufficient IndexedDB quota
-   - Available disk space for SQLite
-   - Backup storage space
-
-4. **Platform Support**
-   - Web: Modern browser with IndexedDB support
-   - iOS: iOS 13+ with SQLite support
-   - Android: Android 5+ with SQLite support
-   - Electron: Latest version with SQLite support
-
-## Migration Process
-
-### 1. Preparation
-
-```typescript
-// src/services/storage/migration/MigrationService.ts
-import initSqlJs from '@jlongster/sql.js';
-import { SQLiteFS } from 'absurd-sql';
-import IndexedDBBackend from 'absurd-sql/dist/indexeddb-backend';
-
-export class MigrationService {
-  private static instance: MigrationService;
-  private backup: MigrationBackup | null = null;
-  private sql: any = null;
-  private db: any = null;
-
-  async prepare(): Promise<void> {
-    try {
-      // 1. Check prerequisites
-      await this.checkPrerequisites();
-      
-      // 2. Create backup
-      this.backup = await this.createBackup();
-      
-      // 3. Verify backup integrity
-      await this.verifyBackup();
-      
-      // 4. Initialize absurd-sql
-      await this.initializeAbsurdSql();
-    } catch (error) {
-      throw new StorageError(
-        'Migration preparation failed',
-        StorageErrorCodes.MIGRATION_FAILED,
-        error
-      );
-    }
-  }
-
-  private async initializeAbsurdSql(): Promise<void> {
-    // Initialize SQL.js
-    this.sql = await initSqlJs({
-      locateFile: (file: string) => {
-        return new URL(`/node_modules/@jlongster/sql.js/dist/${file}`, import.meta.url).href;
-      }
-    });
-
-    // Setup SQLiteFS with IndexedDB backend
-    const sqlFS = new SQLiteFS(this.sql.FS, new IndexedDBBackend());
-    this.sql.register_for_idb(sqlFS);
-
-    // Create and mount filesystem
-    this.sql.FS.mkdir('/sql');
-    this.sql.FS.mount(sqlFS, {}, '/sql');
-
-    // Open database
-    const path = '/sql/db.sqlite';
-    if (typeof SharedArrayBuffer === 'undefined') {
-      let stream = this.sql.FS.open(path, 'a+');
-      await stream.node.contents.readIfFallback();
-      this.sql.FS.close(stream);
-    }
-
-    this.db = new this.sql.Database(path, { filename: true });
-    if (!this.db) {
-      throw new StorageError(
-        'Database initialization failed',
-        StorageErrorCodes.INITIALIZATION_FAILED
-      );
-    }
-
-    // Configure database
-    await this.db.exec(`PRAGMA journal_mode=MEMORY;`);
-  }
-
-  private async checkPrerequisites(): Promise<void> {
-    // Check IndexedDB availability
-    if (!window.indexedDB) {
-      throw new StorageError(
-        'IndexedDB not available',
-        StorageErrorCodes.INITIALIZATION_FAILED
-      );
-    }
-
-    // Check storage quota
-    const quota = await navigator.storage.estimate();
-    if (quota.quota && quota.usage && quota.usage > quota.quota * 0.9) {
-      throw new StorageError(
-        'Insufficient storage space',
-        StorageErrorCodes.STORAGE_FULL
-      );
-    }
-
-    // Check platform support
-    const capabilities = await PlatformDetection.getCapabilities();
-    if (!capabilities.hasFileSystem) {
-      throw new StorageError(
-        'Platform does not support required features',
-        StorageErrorCodes.INITIALIZATION_FAILED
-      );
-    }
-  }
-
-  private async createBackup(): Promise<MigrationBackup> {
-    const dexieDB = new Dexie('TimeSafariDB');
-    
-    return {
-      timestamp: Date.now(),
-      accounts: await dexieDB.accounts.toArray(),
-      settings: await dexieDB.settings.toArray(),
-      contacts: await dexieDB.contacts.toArray(),
-      metadata: {
-        version: '1.0.0',
-        platform: await PlatformDetection.getPlatform(),
-        dexieVersion: Dexie.version
-      }
-    };
-  }
-}
-```
-
-### 2. Data Migration
-
-```typescript
-// src/services/storage/migration/DataMigration.ts
-export class DataMigration {
-  async migrate(backup: MigrationBackup): Promise<void> {
-    try {
-      // 1. Create new database schema
-      await this.createSchema();
-      
-      // 2. Migrate accounts
-      await this.migrateAccounts(backup.accounts);
-      
-      // 3. Migrate settings
-      await this.migrateSettings(backup.settings);
-      
-      // 4. Migrate contacts
-      await this.migrateContacts(backup.contacts);
-      
-      // 5. Verify migration
-      await this.verifyMigration(backup);
-    } catch (error) {
-      // 6. Handle failure
-      await this.handleMigrationFailure(error, backup);
-    }
-  }
-
-  private async migrateAccounts(accounts: Account[]): Promise<void> {
-    // Use transaction for atomicity
-    await this.db.exec('BEGIN TRANSACTION;');
-    try {
-      for (const account of accounts) {
-        await this.db.run(`
-          INSERT INTO accounts (did, public_key_hex, created_at, updated_at)
-          VALUES (?, ?, ?, ?)
-        `, [
-          account.did,
-          account.publicKeyHex,
-          account.createdAt,
-          account.updatedAt
-        ]);
-      }
-      await this.db.exec('COMMIT;');
-    } catch (error) {
-      await this.db.exec('ROLLBACK;');
-      throw error;
-    }
-  }
-
-  private async verifyMigration(backup: MigrationBackup): Promise<void> {
-    // Verify account count
-    const result = await this.db.exec('SELECT COUNT(*) as count FROM accounts');
-    const accountCount = result[0].values[0][0];
-    
-    if (accountCount !== backup.accounts.length) {
-      throw new StorageError(
-        'Account count mismatch',
-        StorageErrorCodes.VERIFICATION_FAILED
-      );
-    }
-
-    // Verify data integrity
-    await this.verifyDataIntegrity(backup);
-  }
-}
-```
-
-### 3. Rollback Strategy
-
-```typescript
-// src/services/storage/migration/RollbackService.ts
-export class RollbackService {
-  async rollback(backup: MigrationBackup): Promise<void> {
-    try {
-      // 1. Stop all database operations
-      await this.stopDatabaseOperations();
-      
-      // 2. Restore from backup
-      await this.restoreFromBackup(backup);
-      
-      // 3. Verify restoration
-      await this.verifyRestoration(backup);
-      
-      // 4. Clean up absurd-sql
-      await this.cleanupAbsurdSql();
-    } catch (error) {
-      throw new StorageError(
-        'Rollback failed',
-        StorageErrorCodes.ROLLBACK_FAILED,
-        error
-      );
-    }
-  }
-
-  private async restoreFromBackup(backup: MigrationBackup): Promise<void> {
-    const dexieDB = new Dexie('TimeSafariDB');
-    
-    // Restore accounts
-    await dexieDB.accounts.bulkPut(backup.accounts);
-    
-    // Restore settings
-    await dexieDB.settings.bulkPut(backup.settings);
-    
-    // Restore contacts
-    await dexieDB.contacts.bulkPut(backup.contacts);
-  }
-}
-```
-
-## Migration UI
-
-```vue
-<!-- src/components/MigrationProgress.vue -->
-<template>
-  <div class="migration-progress">
-    <h2>Database Migration</h2>
-    
-    <div class="progress-container">
-      <div class="progress-bar" :style="{ width: `${progress}%` }" />
-      <div class="progress-text">{{ progress }}%</div>
-    </div>
-    
-    <div class="status-message">{{ statusMessage }}</div>
-    
-    <div v-if="error" class="error-message">
-      {{ error }}
-      <button @click="retryMigration">Retry</button>
-    </div>
-  </div>
-</template>
-
-<script setup lang="ts">
-import { ref, onMounted } from 'vue';
-import { MigrationService } from '@/services/storage/migration/MigrationService';
-
-const progress = ref(0);
-const statusMessage = ref('Preparing migration...');
-const error = ref<string | null>(null);
-
-const migrationService = MigrationService.getInstance();
-
-async function startMigration() {
-  try {
-    // 1. Preparation
-    statusMessage.value = 'Creating backup...';
-    await migrationService.prepare();
-    progress.value = 20;
-    
-    // 2. Data migration
-    statusMessage.value = 'Migrating data...';
-    await migrationService.migrate();
-    progress.value = 80;
-    
-    // 3. Verification
-    statusMessage.value = 'Verifying migration...';
-    await migrationService.verify();
-    progress.value = 100;
-    
-    statusMessage.value = 'Migration completed successfully!';
-  } catch (err) {
-    error.value = err instanceof Error ? err.message : 'Migration failed';
-    statusMessage.value = 'Migration failed';
-  }
-}
-
-async function retryMigration() {
-  error.value = null;
-  progress.value = 0;
-  await startMigration();
-}
-
-onMounted(() => {
-  startMigration();
-});
-</script>
-
-<style scoped>
-.migration-progress {
-  padding: 2rem;
-  max-width: 600px;
-  margin: 0 auto;
-}
-
-.progress-container {
-  position: relative;
-  height: 20px;
-  background: #eee;
-  border-radius: 10px;
-  overflow: hidden;
-  margin: 1rem 0;
-}
-
-.progress-bar {
-  position: absolute;
-  height: 100%;
-  background: #4CAF50;
-  transition: width 0.3s ease;
-}
-
-.progress-text {
-  position: absolute;
-  width: 100%;
-  text-align: center;
-  line-height: 20px;
-  color: #000;
-}
-
-.status-message {
-  text-align: center;
-  margin: 1rem 0;
-}
-
-.error-message {
-  color: #f44336;
-  text-align: center;
-  margin: 1rem 0;
-}
-
-button {
-  margin-top: 1rem;
-  padding: 0.5rem 1rem;
-  background: #2196F3;
-  color: white;
-  border: none;
-  border-radius: 4px;
-  cursor: pointer;
-}
-
-button:hover {
-  background: #1976D2;
-}
-</style>
-```
-
-## Testing Strategy
-
-1. **Unit Tests**
-   ```typescript
-   // src/services/storage/migration/__tests__/MigrationService.spec.ts
-   describe('MigrationService', () => {
-     it('should initialize absurd-sql correctly', async () => {
-       const service = MigrationService.getInstance();
-       await service.initializeAbsurdSql();
-       
-       expect(service.isInitialized()).toBe(true);
-       expect(service.getDatabase()).toBeDefined();
-     });
-
-     it('should create valid backup', async () => {
-       const service = MigrationService.getInstance();
-       const backup = await service.createBackup();
-       
-       expect(backup).toBeDefined();
-       expect(backup.accounts).toBeInstanceOf(Array);
-       expect(backup.settings).toBeInstanceOf(Array);
-       expect(backup.contacts).toBeInstanceOf(Array);
-     });
-
-     it('should migrate data correctly', async () => {
-       const service = MigrationService.getInstance();
-       const backup = await service.createBackup();
-       
-       await service.migrate(backup);
-       
-       // Verify migration
-       const accounts = await service.getMigratedAccounts();
-       expect(accounts).toHaveLength(backup.accounts.length);
-     });
-
-     it('should handle rollback correctly', async () => {
-       const service = MigrationService.getInstance();
-       const backup = await service.createBackup();
-       
-       // Simulate failed migration
-       await service.migrate(backup);
-       await service.simulateFailure();
-       
-       // Perform rollback
-       await service.rollback(backup);
-       
-       // Verify rollback
-       const accounts = await service.getOriginalAccounts();
-       expect(accounts).toHaveLength(backup.accounts.length);
-     });
-   });
-   ```
-
-2. **Integration Tests**
-   ```typescript
-   // src/services/storage/migration/__tests__/integration/Migration.spec.ts
-   describe('Migration Integration', () => {
-     it('should handle concurrent access during migration', async () => {
-       const service = MigrationService.getInstance();
-       
-       // Start migration
-       const migrationPromise = service.migrate();
-       
-       // Simulate concurrent access
-       const accessPromises = Array(5).fill(null).map(() =>
-         service.getAccount('did:test:123')
-       );
-       
-       // Wait for all operations
-       const [migrationResult, ...accessResults] = await Promise.allSettled([
-         migrationPromise,
-         ...accessPromises
-       ]);
-       
-       // Verify results
-       expect(migrationResult.status).toBe('fulfilled');
-       expect(accessResults.some(r => r.status === 'rejected')).toBe(true);
-     });
-
-     it('should maintain data integrity during platform transition', async () => {
-       const service = MigrationService.getInstance();
-       
-       // Simulate platform change
-       await service.simulatePlatformChange();
-       
-       // Verify data
-       const accounts = await service.getAllAccounts();
-       const settings = await service.getAllSettings();
-       const contacts = await service.getAllContacts();
-       
-       expect(accounts).toBeDefined();
-       expect(settings).toBeDefined();
-       expect(contacts).toBeDefined();
-     });
-   });
-   ```
-
-## Success Criteria
-
-1. **Data Integrity**
-   - [ ] All accounts migrated successfully
-   - [ ] All settings preserved
-   - [ ] All contacts transferred
-   - [ ] No data corruption
-
-2. **Performance**
-   - [ ] Migration completes within acceptable time
-   - [ ] No significant performance degradation
-   - [ ] Efficient storage usage
-   - [ ] Smooth user experience
-
-3. **Security**
-   - [ ] Encrypted data remains secure
-   - [ ] Access controls maintained
-   - [ ] No sensitive data exposure
-   - [ ] Secure backup process
-
-4. **User Experience**
-   - [ ] Clear migration progress
-   - [ ] Informative error messages
-   - [ ] Automatic recovery from failures
-   - [ ] No data loss
-
-## Rollback Plan
-
-1. **Automatic Rollback**
-   - Triggered by migration failure
-   - Restores from verified backup
-   - Maintains data consistency
-   - Logs rollback reason
-
-2. **Manual Rollback**
-   - Available through settings
-   - Requires user confirmation
-   - Preserves backup data
-   - Provides rollback status
-
-3. **Emergency Recovery**
-   - Manual backup restoration
-   - Database repair tools
-   - Data recovery procedures
-   - Support contact information
-
-## Post-Migration
-
-1. **Verification**
-   - Data integrity checks
-   - Performance monitoring
-   - Error rate tracking
-   - User feedback collection
-
-2. **Cleanup**
-   - Remove old database
-   - Clear migration artifacts
-   - Update application state
-   - Archive backup data
-
-3. **Monitoring**
-   - Track migration success rate
-   - Monitor performance metrics
-   - Collect error reports
-   - Gather user feedback
-
-## Support
-
-For assistance with migration:
-1. Check the troubleshooting guide
-2. Review error logs
-3. Contact support team
-4. Submit issue report
-
-## Timeline
-
-1. **Preparation Phase** (1 week)
-   - Backup system implementation
-   - Migration service development
-   - Testing framework setup
-
-2. **Testing Phase** (2 weeks)
-   - Unit testing
-   - Integration testing
-   - Performance testing
-   - Security testing
-
-3. **Deployment Phase** (1 week)
-   - Staged rollout
-   - Monitoring
-   - Support preparation
-   - Documentation updates
-
-4. **Post-Deployment** (2 weeks)
-   - Monitoring
-   - Bug fixes
-   - Performance optimization
-   - User feedback collection 

doc/qr-code-implementation-guide.md

@@ -1,805 +0,0 @@
-# QR Code Implementation Guide
-
-## Overview
-
-This document describes the QR code scanning and generation implementation in the TimeSafari application. The system uses a platform-agnostic design with specific implementations for web and mobile platforms.
-
-## Architecture
-
-### Directory Structure
-```
-src/
-├── services/
-│   └── QRScanner/
-│       ├── types.ts              # Core interfaces and types
-│       ├── QRScannerFactory.ts   # Factory for creating scanner instances
-│       ├── CapacitorQRScanner.ts # Mobile implementation using MLKit
-│       ├── WebInlineQRScanner.ts # Web implementation using MediaDevices API
-│       └── interfaces.ts         # Additional interfaces
-├── components/
-│   └── QRScanner/
-│       └── QRScannerDialog.vue   # Shared UI component
-└── views/
-    ├── ContactQRScanView.vue     # Dedicated scanning view
-    └── ContactQRScanShowView.vue # Combined QR display and scanning view
-```
-
-### Core Components
-
-1. **Factory Pattern**
-   - `QRScannerFactory` - Creates appropriate scanner instance based on platform
-   - Common interface `QRScannerService` implemented by all scanners
-   - Platform detection via Capacitor and build flags
-
-2. **Platform-Specific Implementations**
-   - `CapacitorQRScanner` - Native mobile implementation using MLKit
-   - `WebInlineQRScanner` - Web browser implementation using MediaDevices API
-   - `QRScannerDialog.vue` - Shared UI component
-
-3. **View Components**
-   - `ContactQRScanView` - Dedicated view for scanning QR codes
-   - `ContactQRScanShowView` - Combined view for displaying and scanning QR codes
-
-## Implementation Details
-
-### Core Interfaces
-
-```typescript
-interface QRScannerService {
-  checkPermissions(): Promise<boolean>;
-  requestPermissions(): Promise<boolean>;
-  isSupported(): Promise<boolean>;
-  startScan(options?: QRScannerOptions): Promise<void>;
-  stopScan(): Promise<void>;
-  addListener(listener: ScanListener): void;
-  onStream(callback: (stream: MediaStream | null) => void): void;
-  cleanup(): Promise<void>;
-  getAvailableCameras(): Promise<MediaDeviceInfo[]>;
-  switchCamera(deviceId: string): Promise<void>;
-  getCurrentCamera(): Promise<MediaDeviceInfo | null>;
-}
-
-interface ScanListener {
-  onScan: (result: string) => void;
-  onError?: (error: Error) => void;
-}
-
-interface QRScannerOptions {
-  camera?: "front" | "back";
-  showPreview?: boolean;
-  playSound?: boolean;
-}
-```
-
-### Platform-Specific Implementations
-
-#### Mobile (Capacitor)
-- Uses `@capacitor-mlkit/barcode-scanning`
-- Native camera access through platform APIs
-- Optimized for mobile performance
-- Supports both iOS and Android
-- Real-time QR code detection
-- Back camera preferred for scanning
-
-Configuration:
-```typescript
-// capacitor.config.ts
-const config: CapacitorConfig = {
-  plugins: {
-    MLKitBarcodeScanner: {
-      formats: ['QR_CODE'],
-      detectorSize: 1.0,
-      lensFacing: 'back',
-      googleBarcodeScannerModuleInstallState: true,
-      // Additional camera options
-      cameraOptions: {
-        quality: 0.8,
-        allowEditing: false,
-        resultType: 'uri',
-        sourceType: 'CAMERA',
-        saveToGallery: false
-      }
-    }
-  }
-};
-```
-
-#### Web
-- Uses browser's MediaDevices API
-- Vue.js components for UI
-- EventEmitter for stream management
-- Browser-based camera access
-- Inline camera preview
-- Responsive design
-- Cross-browser compatibility
-
-### View Components
-
-#### ContactQRScanView
-- Dedicated view for scanning QR codes
-- Full-screen camera interface
-- Simple UI focused on scanning
-- Used primarily on native platforms
-- Streamlined scanning experience
-
-#### ContactQRScanShowView
-- Combined view for QR code display and scanning
-- Shows user's own QR code
-- Handles user registration status
-- Provides options to copy contact information
-- Platform-specific scanning implementation:
-  - Native: Button to navigate to ContactQRScanView
-  - Web: Built-in scanning functionality
-
-### QR Code Workflow
-
-1. **Initiation**
-   - User selects "Scan QR Code" option
-   - Platform-specific scanner is initialized
-   - Camera permissions are verified
-   - Appropriate scanner component is loaded
-
-2. **Platform-Specific Implementation**
-   - Web: Uses `qrcode-stream` for real-time scanning
-   - Native: Uses `@capacitor-mlkit/barcode-scanning`
-
-3. **Scanning Process**
-   - Camera stream initialization
-   - Real-time frame analysis
-   - QR code detection and decoding
-   - Validation of QR code format
-   - Processing of contact information
-
-4. **Contact Processing**
-   - Decryption of contact data
-   - Validation of user information
-   - Verification of timestamp
-   - Check for duplicate contacts
-   - Processing of shared data
-
-## Build Configuration
-
-### Common Vite Configuration
-```typescript
-// vite.config.common.mts
-export async function createBuildConfig(mode: string) {
-  const isCapacitor = mode === "capacitor";
-  
-  return defineConfig({
-    define: {
-      'process.env.VITE_PLATFORM': JSON.stringify(mode),
-      'process.env.VITE_PWA_ENABLED': JSON.stringify(!isNative),
-      __IS_MOBILE__: JSON.stringify(isCapacitor),
-      __USE_QR_READER__: JSON.stringify(!isCapacitor)
-    },
-    optimizeDeps: {
-      include: [
-        '@capacitor-mlkit/barcode-scanning',
-        'vue-qrcode-reader'
-      ]
-    }
-  });
-}
-```
-
-### Platform-Specific Builds
-```json
-{
-  "scripts": {
-    "build:web": "vite build --config vite.config.web.mts",
-    "build:capacitor": "vite build --config vite.config.capacitor.mts",
-    "build:all": "npm run build:web && npm run build:capacitor"
-  }
-}
-```
-
-## Error Handling
-
-### Common Error Scenarios
-1. No camera found
-2. Permission denied
-3. Camera in use by another application
-4. HTTPS required
-5. Browser compatibility issues
-6. Invalid QR code format
-7. Expired QR codes
-8. Duplicate contact attempts
-9. Network connectivity issues
-
-### Error Response
-- User-friendly error messages
-- Troubleshooting tips
-- Clear instructions for resolution
-- Platform-specific guidance
-
-## Security Considerations
-
-### QR Code Security
-- Encryption of contact data
-- Timestamp validation
-- Version checking
-- User verification
-- Rate limiting for scans
-
-### Data Protection
-- Secure transmission of contact data
-- Validation of QR code authenticity
-- Prevention of duplicate scans
-- Protection against malicious codes
-- Secure storage of contact information
-
-## Best Practices
-
-### Camera Access
-1. Always check for camera availability
-2. Request permissions explicitly
-3. Handle all error conditions
-4. Provide clear user feedback
-5. Implement proper cleanup
-
-### Performance
-1. Optimize camera resolution
-2. Implement proper resource cleanup
-3. Handle camera switching efficiently
-4. Manage memory usage
-5. Battery usage optimization
-
-### User Experience
-1. Clear visual feedback
-2. Camera preview
-3. Scanning status indicators
-4. Error messages
-5. Success confirmations
-6. Intuitive camera controls
-7. Smooth camera switching
-8. Responsive UI feedback
-
-## Testing
-
-### Test Scenarios
-1. Permission handling
-2. Camera switching
-3. Error conditions
-4. Platform compatibility
-5. Performance metrics
-6. QR code detection
-7. Contact processing
-8. Security validation
-
-### Test Environment
-- Multiple browsers
-- iOS and Android devices
-- Various network conditions
-- Different camera configurations
-
-## Dependencies
-
-### Key Packages
-- `@capacitor-mlkit/barcode-scanning`
-- `qrcode-stream`
-- `vue-qrcode-reader`
-- Platform-specific camera APIs
-
-## Maintenance
-
-### Regular Updates
-- Keep dependencies updated
-- Monitor platform changes
-- Update documentation
-- Review security patches
-
-### Performance Monitoring
-- Track memory usage
-- Monitor camera performance
-- Check error rates
-- Analyze user feedback
-
-## Camera Handling
-
-### Camera Switching Implementation
-
-The QR scanner supports camera switching on both mobile and desktop platforms through a unified interface.
-
-#### Platform-Specific Implementations
-
-1. **Mobile (Capacitor)**
-   - Uses `@capacitor-mlkit/barcode-scanning`
-   - Supports front/back camera switching
-   - Native camera access through platform APIs
-   - Optimized for mobile performance
-
-   ```typescript
-   // CapacitorQRScanner.ts
-   async startScan(options?: QRScannerOptions): Promise<void> {
-     const scanOptions: StartScanOptions = {
-       formats: [BarcodeFormat.QrCode],
-       lensFacing: options?.camera === "front" ? 
-         LensFacing.Front : LensFacing.Back
-     };
-     await BarcodeScanner.startScan(scanOptions);
-   }
-   ```
-
-2. **Web (Desktop)**
-   - Uses browser's MediaDevices API
-   - Supports multiple camera devices
-   - Dynamic camera enumeration
-   - Real-time camera switching
-
-   ```typescript
-   // WebInlineQRScanner.ts
-   async getAvailableCameras(): Promise<MediaDeviceInfo[]> {
-     const devices = await navigator.mediaDevices.enumerateDevices();
-     return devices.filter(device => device.kind === 'videoinput');
-   }
-
-   async switchCamera(deviceId: string): Promise<void> {
-     // Stop current stream
-     await this.stopScan();
-     
-     // Start new stream with selected camera
-     this.stream = await navigator.mediaDevices.getUserMedia({
-       video: {
-         deviceId: { exact: deviceId },
-         width: { ideal: 1280 },
-         height: { ideal: 720 }
-       }
-     });
-     
-     // Update video and restart scanning
-     if (this.video) {
-       this.video.srcObject = this.stream;
-       await this.video.play();
-     }
-     this.scanQRCode();
-   }
-   ```
-
-### Core Interfaces
-
-```typescript
-interface QRScannerService {
-  // ... existing methods ...
-
-  /** Get available cameras */
-  getAvailableCameras(): Promise<MediaDeviceInfo[]>;
-  
-  /** Switch to a specific camera */
-  switchCamera(deviceId: string): Promise<void>;
-  
-  /** Get current camera info */
-  getCurrentCamera(): Promise<MediaDeviceInfo | null>;
-}
-
-interface QRScannerOptions {
-  /** Camera to use ('front' or 'back' for mobile) */
-  camera?: "front" | "back";
-  /** Whether to show a preview of the camera feed */
-  showPreview?: boolean;
-  /** Whether to play a sound on successful scan */
-  playSound?: boolean;
-}
-```
-
-### UI Components
-
-The camera switching UI adapts to the platform:
-
-1. **Mobile Interface**
-   - Simple toggle button for front/back cameras
-   - Positioned in bottom-right corner
-   - Clear visual feedback during switching
-   - Native camera controls
-
-   ```vue
-   <button 
-     v-if="isNativePlatform"
-     @click="toggleMobileCamera"
-     class="camera-switch-btn"
-   >
-     <font-awesome icon="camera-rotate" />
-     Switch Camera
-   </button>
-   ```
-
-2. **Desktop Interface**
-   - Dropdown menu with all available cameras
-   - Camera labels and device IDs
-   - Real-time camera switching
-   - Responsive design
-
-   ```vue
-   <select 
-     v-model="selectedCameraId"
-     @change="onCameraChange"
-     class="camera-select-dropdown"
-   >
-     <option 
-       v-for="camera in availableCameras" 
-       :key="camera.deviceId"
-       :value="camera.deviceId"
-     >
-       {{ camera.label || `Camera ${camera.deviceId.slice(0, 4)}` }}
-     </option>
-   </select>
-   ```
-
-### Error Handling
-
-The camera switching implementation includes comprehensive error handling:
-
-1. **Common Error Scenarios**
-   - Camera in use by another application
-   - Permission denied during switch
-   - Device not available
-   - Stream initialization failure
-   - Camera switch timeout
-
-2. **Error Response**
-   ```typescript
-   private async handleCameraSwitch(deviceId: string): Promise<void> {
-     try {
-       this.updateCameraState("initializing", "Switching camera...");
-       await this.switchCamera(deviceId);
-       this.updateCameraState("active", "Camera switched successfully");
-     } catch (error) {
-       this.updateCameraState("error", "Failed to switch camera");
-       throw error;
-     }
-   }
-   ```
-
-3. **User Feedback**
-   - Visual indicators during switching
-   - Error notifications
-   - Camera state updates
-   - Permission request dialogs
-
-### State Management
-
-The camera system maintains several states:
-
-1. **Camera States**
-   ```typescript
-   type CameraState =
-     | "initializing"  // Camera is being initialized
-     | "ready"        // Camera is ready to use
-     | "active"       // Camera is actively streaming
-     | "in_use"       // Camera is in use by another application
-     | "permission_denied" // Camera permission was denied
-     | "not_found"    // No camera found on device
-     | "error"        // Generic error state
-     | "off";         // Camera is off
-   ```
-
-2. **State Transitions**
-   - Initialization → Ready
-   - Ready → Active
-   - Active → Switching
-   - Switching → Active/Error
-   - Any state → Off (on cleanup)
-
-### Best Practices
-
-1. **Camera Access**
-   - Always check permissions before switching
-   - Handle camera busy states
-   - Implement proper cleanup
-   - Monitor camera state changes
-
-2. **Performance**
-   - Optimize camera resolution
-   - Handle stream switching efficiently
-   - Manage memory usage
-   - Implement proper cleanup
-
-3. **User Experience**
-   - Clear visual feedback
-   - Smooth camera transitions
-   - Intuitive camera controls
-   - Responsive UI updates
-   - Accessible camera selection
-
-4. **Security**
-   - Secure camera access
-   - Permission management
-   - Device validation
-   - Stream security
-
-### Testing
-
-1. **Test Scenarios**
-   - Camera switching on both platforms
-   - Permission handling
-   - Error conditions
-   - Multiple camera devices
-   - Camera busy states
-   - Stream initialization
-   - UI responsiveness
-
-2. **Test Environment**
-   - Multiple mobile devices
-   - Various desktop browsers
-   - Different camera configurations
-   - Network conditions
-   - Permission states
-
-### Capacitor Implementation Details
-
-#### MLKit Barcode Scanner Configuration
-
-1. **Plugin Setup**
-   ```typescript
-   // capacitor.config.ts
-   const config: CapacitorConfig = {
-     plugins: {
-       MLKitBarcodeScanner: {
-         formats: ['QR_CODE'],
-         detectorSize: 1.0,
-         lensFacing: 'back',
-         googleBarcodeScannerModuleInstallState: true,
-         // Additional camera options
-         cameraOptions: {
-           quality: 0.8,
-           allowEditing: false,
-           resultType: 'uri',
-           sourceType: 'CAMERA',
-           saveToGallery: false
-         }
-       }
-     }
-   };
-   ```
-
-2. **Camera Management**
-   ```typescript
-   // CapacitorQRScanner.ts
-   export class CapacitorQRScanner implements QRScannerService {
-     private currentLensFacing: LensFacing = LensFacing.Back;
-     
-     async getAvailableCameras(): Promise<MediaDeviceInfo[]> {
-       // On mobile, we have two fixed cameras
-       return [
-         {
-           deviceId: 'back',
-           label: 'Back Camera',
-           kind: 'videoinput'
-         },
-         {
-           deviceId: 'front',
-           label: 'Front Camera',
-           kind: 'videoinput'
-         }
-       ] as MediaDeviceInfo[];
-     }
-
-     async switchCamera(deviceId: string): Promise<void> {
-       if (!this.isScanning) return;
-       
-       const newLensFacing = deviceId === 'front' ? 
-         LensFacing.Front : LensFacing.Back;
-       
-       // Stop current scan
-       await this.stopScan();
-       
-       // Update lens facing
-       this.currentLensFacing = newLensFacing;
-       
-       // Restart scan with new camera
-       await this.startScan({
-         camera: deviceId as 'front' | 'back'
-       });
-     }
-
-     async getCurrentCamera(): Promise<MediaDeviceInfo | null> {
-       return {
-         deviceId: this.currentLensFacing === LensFacing.Front ? 'front' : 'back',
-         label: this.currentLensFacing === LensFacing.Front ? 
-           'Front Camera' : 'Back Camera',
-         kind: 'videoinput'
-       } as MediaDeviceInfo;
-     }
-   }
-   ```
-
-3. **Camera State Management**
-   ```typescript
-   // CapacitorQRScanner.ts
-   private async handleCameraState(): Promise<void> {
-     try {
-       // Check if camera is available
-       const { camera } = await BarcodeScanner.checkPermissions();
-       
-       if (camera === 'denied') {
-         this.updateCameraState('permission_denied');
-         return;
-       }
-       
-       // Check if camera is in use
-       const isInUse = await this.isCameraInUse();
-       if (isInUse) {
-         this.updateCameraState('in_use');
-         return;
-       }
-       
-       this.updateCameraState('ready');
-     } catch (error) {
-       this.updateCameraState('error', error.message);
-     }
-   }
-
-   private async isCameraInUse(): Promise<boolean> {
-     try {
-       // Try to start a test scan
-       await BarcodeScanner.startScan({
-         formats: [BarcodeFormat.QrCode],
-         lensFacing: this.currentLensFacing
-       });
-       // If successful, stop it immediately
-       await BarcodeScanner.stopScan();
-       return false;
-     } catch (error) {
-       return error.message.includes('camera in use');
-     }
-   }
-   ```
-
-4. **Error Handling**
-   ```typescript
-   // CapacitorQRScanner.ts
-   private async handleCameraError(error: Error): Promise<void> {
-     switch (error.name) {
-       case 'CameraPermissionDenied':
-         this.updateCameraState('permission_denied');
-         break;
-       case 'CameraInUse':
-         this.updateCameraState('in_use');
-         break;
-       case 'CameraUnavailable':
-         this.updateCameraState('not_found');
-         break;
-       default:
-         this.updateCameraState('error', error.message);
-     }
-   }
-   ```
-
-#### Platform-Specific Considerations
-
-1. **iOS Implementation**
-   - Camera permissions in Info.plist
-   - Privacy descriptions
-   - Camera usage description
-   - Background camera access
-
-   ```xml
-   <!-- ios/App/App/Info.plist -->
-   <key>NSCameraUsageDescription</key>
-   <string>We need access to your camera to scan QR codes</string>
-   <key>NSPhotoLibraryUsageDescription</key>
-   <string>We need access to save scanned QR codes</string>
-   ```
-
-2. **Android Implementation**
-   - Camera permissions in AndroidManifest.xml
-   - Runtime permission handling
-   - Camera features declaration
-   - Hardware feature requirements
-
-   ```xml
-   <!-- android/app/src/main/AndroidManifest.xml -->
-   <uses-permission android:name="android.permission.CAMERA" />
-   <uses-feature android:name="android.hardware.camera" />
-   <uses-feature android:name="android.hardware.camera.autofocus" />
-   ```
-
-3. **Platform-Specific Features**
-   - iOS: Camera orientation handling
-   - Android: Camera resolution optimization
-   - Both: Battery usage optimization
-   - Both: Memory management
-
-   ```typescript
-   // Platform-specific optimizations
-   private getPlatformSpecificOptions(): StartScanOptions {
-     const baseOptions: StartScanOptions = {
-       formats: [BarcodeFormat.QrCode],
-       lensFacing: this.currentLensFacing
-     };
-
-     if (Capacitor.getPlatform() === 'ios') {
-       return {
-         ...baseOptions,
-         // iOS-specific options
-         cameraOptions: {
-           quality: 0.7, // Lower quality for better performance
-           allowEditing: false,
-           resultType: 'uri'
-         }
-       };
-     } else if (Capacitor.getPlatform() === 'android') {
-       return {
-         ...baseOptions,
-         // Android-specific options
-         cameraOptions: {
-           quality: 0.8,
-           allowEditing: false,
-           resultType: 'uri',
-           saveToGallery: false
-         }
-       };
-     }
-
-     return baseOptions;
-   }
-   ```
-
-#### Performance Optimization
-
-1. **Battery Usage**
-   ```typescript
-   // CapacitorQRScanner.ts
-   private optimizeBatteryUsage(): void {
-     // Reduce scan frequency when battery is low
-     if (this.isLowBattery()) {
-       this.scanInterval = 2000; // 2 seconds between scans
-     } else {
-       this.scanInterval = 1000; // 1 second between scans
-     }
-   }
-
-   private isLowBattery(): boolean {
-     // Check battery level if available
-     if (Capacitor.isPluginAvailable('Battery')) {
-       const { level } = await Battery.getBatteryLevel();
-       return level < 0.2; // 20% or lower
-     }
-     return false;
-   }
-   ```
-
-2. **Memory Management**
-   ```typescript
-   // CapacitorQRScanner.ts
-   private async cleanupResources(): Promise<void> {
-     // Stop scanning
-     await this.stopScan();
-     
-     // Clear any stored camera data
-     this.currentLensFacing = LensFacing.Back;
-     
-     // Remove listeners
-     this.listenerHandles.forEach(handle => handle());
-     this.listenerHandles = [];
-     
-     // Reset state
-     this.isScanning = false;
-     this.updateCameraState('off');
-   }
-   ```
-
-#### Testing on Capacitor
-
-1. **Device Testing**
-   - Test on multiple iOS devices
-   - Test on multiple Android devices
-   - Test different camera configurations
-   - Test with different screen sizes
-   - Test with different OS versions
-
-2. **Camera Testing**
-   - Test front camera switching
-   - Test back camera switching
-   - Test camera permissions
-   - Test camera in use scenarios
-   - Test low light conditions
-   - Test different QR code sizes
-   - Test different QR code distances
-
-3. **Performance Testing**
-   - Battery usage monitoring
-   - Memory usage monitoring
-   - Camera switching speed
-   - QR code detection speed
-   - App responsiveness
-   - Background/foreground transitions

doc/secure-storage-implementation.md

@@ -1,339 +0,0 @@
-# Secure Storage Implementation Guide for TimeSafari App
-
-## Overview
-
-This document outlines the implementation of secure storage for the TimeSafari app. The implementation focuses on:
-
-1. **Platform-Specific Storage Solutions**:
-   - Web: SQLite with IndexedDB backend (absurd-sql)
-   - Electron: SQLite with Node.js backend
-   - Native: (Planned) SQLCipher with platform-specific secure storage
-
-2. **Key Features**:
-   - SQLite-based storage using absurd-sql for web
-   - Platform-specific service factory pattern
-   - Consistent API across platforms
-   - Migration support from Dexie.js
-
-## Quick Start
-
-### 1. Installation
-
-```bash
-# Core dependencies
-npm install @jlongster/sql.js
-npm install absurd-sql
-
-# Platform-specific dependencies (for future native support)
-npm install @capacitor/preferences
-npm install @capacitor-community/biometric-auth
-```
-
-### 2. Basic Usage
-
-```typescript
-// Using the platform service
-import { PlatformServiceFactory } from '../services/PlatformServiceFactory';
-
-// Get platform-specific service instance
-const platformService = PlatformServiceFactory.getInstance();
-
-// Example database operations
-async function example() {
-  try {
-    // Query example
-    const result = await platformService.dbQuery(
-      "SELECT * FROM accounts WHERE did = ?",
-      [did]
-    );
-
-    // Execute example
-    await platformService.dbExec(
-      "INSERT INTO accounts (did, public_key_hex) VALUES (?, ?)",
-      [did, publicKeyHex]
-    );
-
-    } catch (error) {
-    console.error('Database operation failed:', error);
-  }
-}
-```
-
-### 3. Platform Detection
-
-```typescript
-// src/services/PlatformServiceFactory.ts
-export class PlatformServiceFactory {
-  static getInstance(): PlatformService {
-    if (process.env.ELECTRON) {
-      // Electron platform
-      return new ElectronPlatformService();
-    } else {
-      // Web platform (default)
-      return new AbsurdSqlDatabaseService();
-    }
-  }
-}
-```
-
-### 4. Current Implementation Details
-
-#### Web Platform (AbsurdSqlDatabaseService)
-
-The web platform uses absurd-sql with IndexedDB backend:
-
-```typescript
-// src/services/AbsurdSqlDatabaseService.ts
-export class AbsurdSqlDatabaseService implements PlatformService {
-  private static instance: AbsurdSqlDatabaseService | null = null;
-  private db: AbsurdSqlDatabase | null = null;
-  private initialized: boolean = false;
-      
-  // Singleton pattern
-  static getInstance(): AbsurdSqlDatabaseService {
-    if (!AbsurdSqlDatabaseService.instance) {
-      AbsurdSqlDatabaseService.instance = new AbsurdSqlDatabaseService();
-    }
-    return AbsurdSqlDatabaseService.instance;
-  }
-
-  // Database operations
-  async dbQuery(sql: string, params: unknown[] = []): Promise<QueryExecResult[]> {
-    await this.waitForInitialization();
-    return this.queueOperation<QueryExecResult[]>("query", sql, params);
-    }
-
-  async dbExec(sql: string, params: unknown[] = []): Promise<void> {
-    await this.waitForInitialization();
-    await this.queueOperation<void>("run", sql, params);
-  }
-}
-```
-
-Key features:
-- Uses absurd-sql for SQLite in the browser
-- Implements operation queuing for thread safety
-- Handles initialization and connection management
-- Provides consistent API across platforms
-
-### 5. Migration from Dexie.js
-
-The current implementation supports gradual migration from Dexie.js:
-
-```typescript
-// Example of dual-storage pattern
-async function getAccount(did: string): Promise<Account | undefined> {
-  // Try SQLite first
-  const platform = PlatformServiceFactory.getInstance();
-  let account = await platform.dbQuery(
-    "SELECT * FROM accounts WHERE did = ?",
-    [did]
-  );
-
-  // Fallback to Dexie if needed
-  if (USE_DEXIE_DB) {
-    account = await db.accounts.get(did);
-  }
-
-  return account;
-   }
-```
-
-#### A. Modifying Code
-
-When converting from Dexie.js to SQL-based implementation, follow these patterns:
-
-1. **Database Access Pattern**
-   ```typescript
-   // Before (Dexie)
-   const result = await db.table.where("field").equals(value).first();
-
-   // After (SQL)
-   const platform = PlatformServiceFactory.getInstance();
-   let result = await platform.dbQuery(
-     "SELECT * FROM table WHERE field = ?",
-     [value]
-   );
-   result = databaseUtil.mapQueryResultToValues(result);
-   
-   // Fallback to Dexie if needed
-   if (USE_DEXIE_DB) {
-     result = await db.table.where("field").equals(value).first();
-   }
-   ```
-
-2. **Update Operations**
-   ```typescript
-   // Before (Dexie)
-   await db.table.where("id").equals(id).modify(changes);
-
-   // After (SQL)
-   // For settings updates, use the utility methods:
-   await databaseUtil.updateDefaultSettings(changes);
-   // OR
-   await databaseUtil.updateAccountSettings(did, changes);
-
-   // For other tables, use direct SQL:
-   const platform = PlatformServiceFactory.getInstance();
-   await platform.dbExec(
-     "UPDATE table SET field1 = ?, field2 = ? WHERE id = ?",
-     [changes.field1, changes.field2, id]
-   );
-
-   // Fallback to Dexie if needed
-   if (USE_DEXIE_DB) {
-     await db.table.where("id").equals(id).modify(changes);
-   }
-   ```
-
-3. **Insert Operations**
-   ```typescript
-   // Before (Dexie)
-   await db.table.add(item);
-
-   // After (SQL)
-   const platform = PlatformServiceFactory.getInstance();
-   const columns = Object.keys(item);
-   const values = Object.values(item);
-   const placeholders = values.map(() => '?').join(', ');
-   const sql = `INSERT INTO table (${columns.join(', ')}) VALUES (${placeholders})`;
-   await platform.dbExec(sql, values);
-
-   // Fallback to Dexie if needed
-   if (USE_DEXIE_DB) {
-     await db.table.add(item);
-   }
-   ```
-
-4. **Delete Operations**
-   ```typescript
-   // Before (Dexie)
-   await db.table.where("id").equals(id).delete();
-
-   // After (SQL)
-   const platform = PlatformServiceFactory.getInstance();
-   await platform.dbExec("DELETE FROM table WHERE id = ?", [id]);
-
-   // Fallback to Dexie if needed
-   if (USE_DEXIE_DB) {
-     await db.table.where("id").equals(id).delete();
-   }
-   ```
-
-5. **Result Processing**
-   ```typescript
-   // Before (Dexie)
-   const items = await db.table.toArray();
-
-   // After (SQL)
-   const platform = PlatformServiceFactory.getInstance();
-   let items = await platform.dbQuery("SELECT * FROM table");
-   items = databaseUtil.mapQueryResultToValues(items);
-
-   // Fallback to Dexie if needed
-   if (USE_DEXIE_DB) {
-     items = await db.table.toArray();
-   }
-   ```
-
-6. **Using Utility Methods**
-
-When working with settings or other common operations, use the utility methods in `db/index.ts`:
-
-```typescript
-// Settings operations
-await databaseUtil.updateDefaultSettings(settings);
-await databaseUtil.updateAccountSettings(did, settings);
-const settings = await databaseUtil.retrieveSettingsForDefaultAccount();
-const settings = await databaseUtil.retrieveSettingsForActiveAccount();
-
-// Logging operations
-await databaseUtil.logToDb(message);
-await databaseUtil.logConsoleAndDb(message, showInConsole);
-```
-
-Key Considerations:
-- Always use `databaseUtil.mapQueryResultToValues()` to process SQL query results
-- Use utility methods from `db/index.ts` when available instead of direct SQL
-- Keep Dexie fallbacks wrapped in `if (USE_DEXIE_DB)` checks
-- For queries that return results, use `let` variables to allow Dexie fallback to override
-- For updates/inserts/deletes, execute both SQL and Dexie operations when `USE_DEXIE_DB` is true
-
-Example Migration:
-```typescript
-// Before (Dexie)
-export async function updateSettings(settings: Settings): Promise<void> {
-  await db.settings.put(settings);
-}
-
-// After (SQL)
-export async function updateSettings(settings: Settings): Promise<void> {
-  const platform = PlatformServiceFactory.getInstance();
-  const { sql, params } = generateUpdateStatement(
-    settings,
-    "settings",
-    "id = ?",
-    [settings.id]
-  );
-  await platform.dbExec(sql, params);
-}
-```
-
-Remember to:
-- Create database access code to use the platform service, putting it in front of the Dexie version
-- Instead of removing Dexie-specific code, keep it.
-
-  - For creates & updates & deletes, the duplicate code is fine.
-
-  - For queries where we use the results, make the setting from SQL into a 'let' variable, then wrap the Dexie code in a check for USE_DEXIE_DB from app.ts and if
-it's true then use that result instead of the SQL code's result.
-
-- Consider data migration needs, and warn if there are any potential migration problems
-
-## Success Criteria
-
-1. **Functionality**
-   - [x] Basic CRUD operations work correctly
-   - [x] Platform service factory pattern implemented
-   - [x] Error handling in place
-   - [ ] Native platform support (planned)
-
-2. **Performance**
-   - [x] Database operations complete within acceptable time
-   - [x] Operation queuing for thread safety
-   - [x] Proper initialization handling
-   - [ ] Performance monitoring (planned)
-
-3. **Security**
-   - [x] Basic data integrity
-   - [ ] Encryption (planned for native platforms)
-   - [ ] Secure key storage (planned)
-   - [ ] Platform-specific security features (planned)
-
-4. **Testing**
-   - [x] Basic unit tests
-   - [ ] Comprehensive integration tests (planned)
-   - [ ] Platform-specific tests (planned)
-   - [ ] Migration tests (planned)
-
-## Next Steps
-
-1. **Native Platform Support**
-   - Implement SQLCipher for iOS/Android
-   - Add platform-specific secure storage
-   - Implement biometric authentication
-
-2. **Enhanced Security**
-   - Add encryption for sensitive data
-   - Implement secure key storage
-   - Add platform-specific security features
-
-3. **Testing and Monitoring**
-   - Add comprehensive test coverage
-   - Implement performance monitoring
-   - Add error tracking and analytics
-
-4. **Documentation**
-   - Add API documentation
-   - Create migration guides
-   - Document security measures

doc/storage-implementation-checklist.md

@@ -1,329 +0,0 @@
-# Storage Implementation Checklist
-
-## Core Services
-
-### 1. Storage Service Layer
-- [x] Create base `PlatformService` interface
-  - [x] Define common methods for all platforms
-  - [x] Add platform-specific method signatures
-  - [x] Include error handling types
-  - [x] Add migration support methods
-
-- [x] Implement platform-specific services
-  - [x] `AbsurdSqlDatabaseService` (web)
-    - [x] Database initialization
-    - [x] VFS setup with IndexedDB backend
-    - [x] Connection management
-    - [x] Operation queuing
-  - [ ] `NativeSQLiteService` (iOS/Android) (planned)
-    - [ ] SQLCipher integration
-    - [ ] Native bridge setup
-    - [ ] File system access
-  - [ ] `ElectronSQLiteService` (planned)
-    - [ ] Node SQLite integration
-    - [ ] IPC communication
-    - [ ] File system access
-
-### 2. Migration Services
-- [x] Implement basic migration support
-  - [x] Dual-storage pattern (SQLite + Dexie)
-  - [x] Basic data verification
-  - [ ] Rollback procedures (planned)
-  - [ ] Progress tracking (planned)
-- [ ] Create `MigrationUI` components (planned)
-  - [ ] Progress indicators
-  - [ ] Error handling
-  - [ ] User notifications
-  - [ ] Manual triggers
-
-### 3. Security Layer
-- [x] Basic data integrity
-- [ ] Implement `EncryptionService` (planned)
-  - [ ] Key management
-  - [ ] Encryption/decryption
-  - [ ] Secure storage
-- [ ] Add `BiometricService` (planned)
-  - [ ] Platform detection
-  - [ ] Authentication flow
-  - [ ] Fallback mechanisms
-
-## Platform-Specific Implementation
-
-### Web Platform
-- [x] Setup absurd-sql
-  - [x] Install dependencies
-    ```json
-    {
-      "@jlongster/sql.js": "^1.8.0",
-      "absurd-sql": "^1.8.0"
-    }
-    ```
-  - [x] Configure VFS with IndexedDB backend
-  - [x] Setup worker threads
-  - [x] Implement operation queuing
-  - [x] Configure database pragmas
-  
-    ```sql
-    PRAGMA journal_mode=MEMORY;
-    PRAGMA synchronous=NORMAL;
-    PRAGMA foreign_keys=ON;
-    PRAGMA busy_timeout=5000;
-    ```
-
-- [x] Update build configuration
-  - [x] Modify `vite.config.ts`
-  - [x] Add worker configuration
-  - [x] Update chunk splitting
-  - [x] Configure asset handling
-
-- [x] Implement IndexedDB backend
-  - [x] Create database service
-  - [x] Add operation queuing
-  - [x] Handle initialization
-  - [x] Implement atomic operations
-
-### iOS Platform (Planned)
-- [ ] Setup SQLCipher
-  - [ ] Install pod dependencies
-  - [ ] Configure encryption
-  - [ ] Setup keychain access
-  - [ ] Implement secure storage
-
-- [ ] Update Capacitor config
-  - [ ] Modify `capacitor.config.ts`
-  - [ ] Add iOS permissions
-  - [ ] Configure backup
-  - [ ] Setup app groups
-
-### Android Platform (Planned)
-- [ ] Setup SQLCipher
-  - [ ] Add Gradle dependencies
-  - [ ] Configure encryption
-  - [ ] Setup keystore
-  - [ ] Implement secure storage
-
-- [ ] Update Capacitor config
-  - [ ] Modify `capacitor.config.ts`
-  - [ ] Add Android permissions
-  - [ ] Configure backup
-  - [ ] Setup file provider
-
-### Electron Platform (Planned)
-- [ ] Setup Node SQLite
-  - [ ] Install dependencies
-  - [ ] Configure IPC
-  - [ ] Setup file system access
-  - [ ] Implement secure storage
-
-- [ ] Update Electron config
-  - [ ] Modify `electron.config.ts`
-  - [ ] Add security policies
-  - [ ] Configure file access
-  - [ ] Setup auto-updates
-
-## Data Models and Types
-
-### 1. Database Schema
-- [x] Define tables
-
-  ```sql
-  -- Accounts table
-  CREATE TABLE accounts (
-    did TEXT PRIMARY KEY,
-    public_key_hex TEXT NOT NULL,
-    created_at INTEGER NOT NULL,
-    updated_at INTEGER NOT NULL
-  );
-
-  -- Settings table
-  CREATE TABLE settings (
-    key TEXT PRIMARY KEY,
-    value TEXT NOT NULL,
-    updated_at INTEGER NOT NULL
-  );
-
-  -- Contacts table
-  CREATE TABLE contacts (
-    id TEXT PRIMARY KEY,
-    did TEXT NOT NULL,
-    name TEXT,
-    created_at INTEGER NOT NULL,
-    updated_at INTEGER NOT NULL,
-    FOREIGN KEY (did) REFERENCES accounts(did)
-  );
-
-  -- Indexes for performance
-  CREATE INDEX idx_accounts_created_at ON accounts(created_at);
-  CREATE INDEX idx_contacts_did ON contacts(did);
-  CREATE INDEX idx_settings_updated_at ON settings(updated_at);
-  ```
-
-- [x] Create indexes
-- [x] Define constraints
-- [ ] Add triggers (planned)
-- [ ] Setup migrations (planned)
-
-### 2. Type Definitions
-
-- [x] Create interfaces
-  ```typescript
-  interface Account {
-    did: string;
-    publicKeyHex: string;
-    createdAt: number;
-    updatedAt: number;
-  }
-
-  interface Setting {
-    key: string;
-    value: string;
-    updatedAt: number;
-  }
-
-  interface Contact {
-    id: string;
-    did: string;
-    name?: string;
-    createdAt: number;
-    updatedAt: number;
-  }
-  ```
-
-- [x] Add validation
-- [x] Create DTOs
-- [x] Define enums
-- [x] Add type guards
-
-## UI Components
-
-### 1. Migration UI (Planned)
-- [ ] Create components
-  - [ ] `MigrationProgress.vue`
-  - [ ] `MigrationError.vue`
-  - [ ] `MigrationSettings.vue`
-  - [ ] `MigrationStatus.vue`
-
-### 2. Settings UI (Planned)
-- [ ] Update components
-  - [ ] Add storage settings
-  - [ ] Add migration controls
-  - [ ] Add backup options
-  - [ ] Add security settings
-
-### 3. Error Handling UI (Planned)
-- [ ] Create components
-  - [ ] `StorageError.vue`
-  - [ ] `QuotaExceeded.vue`
-  - [ ] `MigrationFailed.vue`
-  - [ ] `RecoveryOptions.vue`
-
-## Testing
-
-### 1. Unit Tests
-- [x] Basic service tests
-  - [x] Platform service tests
-  - [x] Database operation tests
-  - [ ] Security service tests (planned)
-  - [ ] Platform detection tests (planned)
-
-### 2. Integration Tests (Planned)
-- [ ] Test migrations
-  - [ ] Web platform tests
-  - [ ] iOS platform tests
-  - [ ] Android platform tests
-  - [ ] Electron platform tests
-
-### 3. E2E Tests (Planned)
-- [ ] Test workflows
-  - [ ] Account management
-  - [ ] Settings management
-  - [ ] Contact management
-  - [ ] Migration process
-
-## Documentation
-
-### 1. Technical Documentation
-- [x] Update architecture docs
-- [x] Add API documentation
-- [ ] Create migration guides (planned)
-- [ ] Document security measures (planned)
-
-### 2. User Documentation (Planned)
-- [ ] Update user guides
-- [ ] Add troubleshooting guides
-- [ ] Create FAQ
-- [ ] Document new features
-
-## Deployment
-
-### 1. Build Process
-- [x] Update build scripts
-- [x] Add platform-specific builds
-- [ ] Configure CI/CD (planned)
-- [ ] Setup automated testing (planned)
-
-### 2. Release Process (Planned)
-- [ ] Create release checklist
-- [ ] Add version management
-- [ ] Setup rollback procedures
-- [ ] Configure monitoring
-
-## Monitoring and Analytics (Planned)
-
-### 1. Error Tracking
-- [ ] Setup error logging
-- [ ] Add performance monitoring
-- [ ] Configure alerts
-- [ ] Create dashboards
-
-### 2. Usage Analytics
-- [ ] Add storage metrics
-- [ ] Track migration success
-- [ ] Monitor performance
-- [ ] Collect user feedback
-
-## Security Audit (Planned)
-
-### 1. Code Review
-- [ ] Review encryption
-- [ ] Check access controls
-- [ ] Verify data handling
-- [ ] Audit dependencies
-
-### 2. Penetration Testing
-- [ ] Test data access
-- [ ] Verify encryption
-- [ ] Check authentication
-- [ ] Review permissions
-
-## Success Criteria
-
-### 1. Performance
-- [x] Query response time < 100ms
-- [x] Operation queuing for thread safety
-- [x] Proper initialization handling
-- [ ] Migration time < 5s per 1000 records (planned)
-- [ ] Storage overhead < 10% (planned)
-- [ ] Memory usage < 50MB (planned)
-
-### 2. Reliability
-- [x] Basic data integrity
-- [x] Operation queuing
-- [ ] Automatic recovery (planned)
-- [ ] Backup verification (planned)
-- [ ] Transaction atomicity (planned)
-- [ ] Data consistency (planned)
-
-### 3. Security
-- [x] Basic data integrity
-- [ ] AES-256 encryption (planned)
-- [ ] Secure key storage (planned)
-- [ ] Access control (planned)
-- [ ] Audit logging (planned)
-
-### 4. User Experience
-- [x] Basic database operations
-- [ ] Smooth migration (planned)
-- [ ] Clear error messages (planned)
-- [ ] Progress indicators (planned)
-- [ ] Recovery options (planned) 

docs/DEEP_LINKS.md

@@ -9,95 +9,21 @@ The deep linking system uses a multi-layered type safety approach:
    - Enforces parameter requirements
    - Sanitizes input data
    - Provides detailed validation errors
-   - Generates TypeScript types automatically
 
 2. **TypeScript Types**
-   - Generated from Zod schemas using `z.infer`
+   - Generated from Zod schemas
    - Ensures compile-time type safety
    - Provides IDE autocompletion
    - Catches type errors during development
-   - Maintains single source of truth for types
 
 3. **Router Integration**
    - Type-safe parameter passing
    - Route-specific parameter validation
    - Query parameter type checking
-   - Automatic type inference for route parameters
-
-## Type System Implementation
-
-### Zod Schema to TypeScript Type Generation
-
-```typescript
-// Define the schema
-const claimSchema = z.object({
-  id: z.string(),
-  view: z.enum(["details", "certificate", "raw"]).optional()
-});
-
-// TypeScript type is automatically generated
-type ClaimParams = z.infer<typeof claimSchema>;
-// Equivalent to:
-// type ClaimParams = {
-//   id: string;
-//   view?: "details" | "certificate" | "raw";
-// }
-```
-
-### Type Safety Layers
-
-1. **Schema Definition**
-   ```typescript
-   // src/interfaces/deepLinks.ts
-   export const deepLinkSchemas = {
-     claim: z.object({
-       id: z.string(),
-       view: z.enum(["details", "certificate", "raw"]).optional()
-     }),
-     // Other route schemas...
-   };
-   ```
-
-2. **Type Generation**
-   ```typescript
-   // Types are automatically generated from schemas
-   export type DeepLinkParams = {
-     [K in keyof typeof deepLinkSchemas]: z.infer<(typeof deepLinkSchemas)[K]>;
-   };
-   ```
-
-3. **Runtime Validation**
-   ```typescript
-   // In DeepLinkHandler
-   const result = deepLinkSchemas.claim.safeParse(params);
-   if (!result.success) {
-     // Handle validation errors
-     console.error(result.error);
-   }
-   ```
-
-### Error Handling Types
-
-```typescript
-export interface DeepLinkError extends Error {
-  code: string;
-  details?: unknown;
-}
-
-// Usage in error handling
-try {
-  await handler.handleDeepLink(url);
-} catch (error) {
-  if (error instanceof DeepLinkError) {
-    // Type-safe error handling
-    console.error(error.code, error.message);
-  }
-}
-```
 
 ## Implementation Files
 
-- `src/interfaces/deepLinks.ts`: Type definitions and validation schemas
+- `src/types/deepLinks.ts`: Type definitions and validation schemas
 - `src/services/deepLinks.ts`: Deep link processing service
 - `src/main.capacitor.ts`: Capacitor integration
 

index.html

@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
-    <meta name="viewport" content="width=device-width,initial-scale=1.0,viewport-fit=cover">
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
     <link rel="icon" href="/favicon.ico">
     <title>TimeSafari</title>
   </head>

ios/.gitignore

@@ -4,6 +4,7 @@ App/output
 App/App/public
 DerivedData
 xcuserdata
+*.xcuserstate
 
 # Cordova plugins for Capacitor
 capacitor-cordova-ios-plugins
@@ -20,7 +21,3 @@ fastlane/report.xml
 fastlane/Preview.html
 fastlane/screenshots
 fastlane/test_output
-
-# Generated Icons from capacitor-assets (also Contents.json which is confusing; see BUILDING.md)
-App/App/Assets.xcassets/AppIcon.appiconset
-App/App/Assets.xcassets/Splash.imageset

ios/App/App.xcworkspace/contents.xcworkspacedata

@@ -2,7 +2,7 @@
 <Workspace
    version = "1.0">
    <FileRef
-      location = "group:App.xcodeproj">
+      location = "group:Time Safari.xcodeproj">
    </FileRef>
    <FileRef
       location = "group:Pods/Pods.xcodeproj">

ios/App/App/AppDelegate.swift

@@ -1,6 +1,5 @@
 import UIKit
 import Capacitor
-import CapacitorCommunitySqlite
 
 @UIApplicationMain
 class AppDelegate: UIResponder, UIApplicationDelegate {
@@ -8,10 +7,6 @@ class AppDelegate: UIResponder, UIApplicationDelegate {
     var window: UIWindow?
 
     func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
-        // Initialize SQLite
-        //let sqlite = SQLite()
-        //sqlite.initialize()
-        
         // Override point for customization after application launch.
         return true
     }

ios/App/App/Assets.xcassets/AppIcon.appiconset/Contents.json

@@ -0,0 +1,14 @@
+{
+  "images": [
+    {
+      "idiom": "universal",
+      "size": "1024x1024",
+      "filename": "AppIcon-512@2x.png",
+      "platform": "ios"
+    }
+  ],
+  "info": {
+    "author": "xcode",
+    "version": 1
+  }
+}

ios/App/App/Assets.xcassets/Splash.imageset/Contents.json

@@ -0,0 +1,23 @@
+{
+  "images" : [
+    {
+      "idiom" : "universal",
+      "filename" : "splash-2732x2732-2.png",
+      "scale" : "1x"
+    },
+    {
+      "idiom" : "universal",
+      "filename" : "splash-2732x2732-1.png",
+      "scale" : "2x"
+    },
+    {
+      "idiom" : "universal",
+      "filename" : "splash-2732x2732.png",
+      "scale" : "3x"
+    }
+  ],
+  "info" : {
+    "version" : 1,
+    "author" : "xcode"
+  }
+}

ios/App/App/Info.plist

@@ -5,7 +5,7 @@
 	<key>CFBundleDevelopmentRegion</key>
 	<string>en</string>
 	<key>CFBundleDisplayName</key>
-	<string>TimeSafari</string>
+        <string>TimeSafari</string>
 	<key>CFBundleExecutable</key>
 	<string>$(EXECUTABLE_NAME)</string>
 	<key>CFBundleIdentifier</key>
@@ -22,10 +22,6 @@
 	<string>$(CURRENT_PROJECT_VERSION)</string>
 	<key>LSRequiresIPhoneOS</key>
 	<true/>
-	<key>NSCameraUsageDescription</key>
-	<string>Time Safari allows you to take photos, and also scan QR codes from contacts.</string>
-	<key>NSPhotoLibraryUsageDescription</key>
-	<string>Time Safari allows you to upload photos.</string>
 	<key>UILaunchStoryboardName</key>
 	<string>LaunchScreen</string>
 	<key>UIMainStoryboardFile</key>

ios/App/App/entitlements.mac.plist

@@ -1,20 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<plist version="1.0">
-  <dict>
-    <key>com.apple.security.cs.allow-jit</key>
-    <true/>
-    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
-    <true/>
-    <key>com.apple.security.cs.debugger</key>
-    <true/>
-    <key>com.apple.security.device.audio-input</key>
-    <true/>
-    <key>com.apple.security.device.camera</key>
-    <true/>
-    <key>com.apple.security.personal-information.addressbook</key>
-    <true/>
-    <key>com.apple.security.personal-information.calendars</key>
-    <true/>
-  </dict>
-</plist>

ios/App/Podfile

@@ -11,13 +11,7 @@ install! 'cocoapods', :disable_input_output_paths => true
 def capacitor_pods
   pod 'Capacitor', :path => '../../node_modules/@capacitor/ios'
   pod 'CapacitorCordova', :path => '../../node_modules/@capacitor/ios'
-  pod 'CapacitorCommunitySqlite', :path => '../../node_modules/@capacitor-community/sqlite'
-  pod 'CapacitorMlkitBarcodeScanning', :path => '../../node_modules/@capacitor-mlkit/barcode-scanning'
   pod 'CapacitorApp', :path => '../../node_modules/@capacitor/app'
-  pod 'CapacitorCamera', :path => '../../node_modules/@capacitor/camera'
-  pod 'CapacitorFilesystem', :path => '../../node_modules/@capacitor/filesystem'
-  pod 'CapacitorShare', :path => '../../node_modules/@capacitor/share'
-  pod 'CapawesomeCapacitorFilePicker', :path => '../../node_modules/@capawesome/capacitor-file-picker'
 end
 
 target 'App' do
@@ -27,9 +21,4 @@ end
 
 post_install do |installer|
   assertDeploymentTarget(installer)
-  installer.pods_project.targets.each do |target|
-    target.build_configurations.each do |config|
-      config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
-    end
-  end
 end

ios/App/Podfile.lock

@@ -1,162 +1,28 @@
 PODS:
-  - Capacitor (6.2.1):
+  - Capacitor (6.2.0):
     - CapacitorCordova
   - CapacitorApp (6.0.2):
     - Capacitor
-  - CapacitorCamera (6.1.2):
-    - Capacitor
-  - CapacitorCommunitySqlite (6.0.2):
-    - Capacitor
-    - SQLCipher
-    - ZIPFoundation
-  - CapacitorCordova (6.2.1)
-  - CapacitorFilesystem (6.0.3):
-    - Capacitor
-  - CapacitorMlkitBarcodeScanning (6.2.0):
-    - Capacitor
-    - GoogleMLKit/BarcodeScanning (= 5.0.0)
-  - CapacitorShare (6.0.3):
-    - Capacitor
-  - CapawesomeCapacitorFilePicker (6.2.0):
-    - Capacitor
-  - GoogleDataTransport (9.4.1):
-    - GoogleUtilities/Environment (~> 7.7)
-    - nanopb (< 2.30911.0, >= 2.30908.0)
-    - PromisesObjC (< 3.0, >= 1.2)
-  - GoogleMLKit/BarcodeScanning (5.0.0):
-    - GoogleMLKit/MLKitCore
-    - MLKitBarcodeScanning (~> 4.0.0)
-  - GoogleMLKit/MLKitCore (5.0.0):
-    - MLKitCommon (~> 10.0.0)
-  - GoogleToolboxForMac/DebugUtils (2.3.2):
-    - GoogleToolboxForMac/Defines (= 2.3.2)
-  - GoogleToolboxForMac/Defines (2.3.2)
-  - GoogleToolboxForMac/Logger (2.3.2):
-    - GoogleToolboxForMac/Defines (= 2.3.2)
-  - "GoogleToolboxForMac/NSData+zlib (2.3.2)":
-    - GoogleToolboxForMac/Defines (= 2.3.2)
-  - "GoogleToolboxForMac/NSDictionary+URLArguments (2.3.2)":
-    - GoogleToolboxForMac/DebugUtils (= 2.3.2)
-    - GoogleToolboxForMac/Defines (= 2.3.2)
-    - "GoogleToolboxForMac/NSString+URLArguments (= 2.3.2)"
-  - "GoogleToolboxForMac/NSString+URLArguments (2.3.2)"
-  - GoogleUtilities/Environment (7.13.3):
-    - GoogleUtilities/Privacy
-    - PromisesObjC (< 3.0, >= 1.2)
-  - GoogleUtilities/Logger (7.13.3):
-    - GoogleUtilities/Environment
-    - GoogleUtilities/Privacy
-  - GoogleUtilities/Privacy (7.13.3)
-  - GoogleUtilities/UserDefaults (7.13.3):
-    - GoogleUtilities/Logger
-    - GoogleUtilities/Privacy
-  - GoogleUtilitiesComponents (1.1.0):
-    - GoogleUtilities/Logger
-  - GTMSessionFetcher/Core (3.5.0)
-  - MLImage (1.0.0-beta5)
-  - MLKitBarcodeScanning (4.0.0):
-    - MLKitCommon (~> 10.0)
-    - MLKitVision (~> 6.0)
-  - MLKitCommon (10.0.0):
-    - GoogleDataTransport (~> 9.0)
-    - GoogleToolboxForMac/Logger (~> 2.1)
-    - "GoogleToolboxForMac/NSData+zlib (~> 2.1)"
-    - "GoogleToolboxForMac/NSDictionary+URLArguments (~> 2.1)"
-    - GoogleUtilities/UserDefaults (~> 7.0)
-    - GoogleUtilitiesComponents (~> 1.0)
-    - GTMSessionFetcher/Core (< 4.0, >= 1.1)
-  - MLKitVision (6.0.0):
-    - GoogleToolboxForMac/Logger (~> 2.1)
-    - "GoogleToolboxForMac/NSData+zlib (~> 2.1)"
-    - GTMSessionFetcher/Core (< 4.0, >= 1.1)
-    - MLImage (= 1.0.0-beta5)
-    - MLKitCommon (~> 10.0)
-  - nanopb (2.30910.0):
-    - nanopb/decode (= 2.30910.0)
-    - nanopb/encode (= 2.30910.0)
-  - nanopb/decode (2.30910.0)
-  - nanopb/encode (2.30910.0)
-  - PromisesObjC (2.4.0)
-  - SQLCipher (4.9.0):
-    - SQLCipher/standard (= 4.9.0)
-  - SQLCipher/common (4.9.0)
-  - SQLCipher/standard (4.9.0):
-    - SQLCipher/common
-  - ZIPFoundation (0.9.19)
+  - CapacitorCordova (6.2.0)
 
 DEPENDENCIES:
   - "Capacitor (from `../../node_modules/@capacitor/ios`)"
   - "CapacitorApp (from `../../node_modules/@capacitor/app`)"
-  - "CapacitorCamera (from `../../node_modules/@capacitor/camera`)"
-  - "CapacitorCommunitySqlite (from `../../node_modules/@capacitor-community/sqlite`)"
   - "CapacitorCordova (from `../../node_modules/@capacitor/ios`)"
-  - "CapacitorFilesystem (from `../../node_modules/@capacitor/filesystem`)"
-  - "CapacitorMlkitBarcodeScanning (from `../../node_modules/@capacitor-mlkit/barcode-scanning`)"
-  - "CapacitorShare (from `../../node_modules/@capacitor/share`)"
-  - "CapawesomeCapacitorFilePicker (from `../../node_modules/@capawesome/capacitor-file-picker`)"
-
-SPEC REPOS:
-  trunk:
-    - GoogleDataTransport
-    - GoogleMLKit
-    - GoogleToolboxForMac
-    - GoogleUtilities
-    - GoogleUtilitiesComponents
-    - GTMSessionFetcher
-    - MLImage
-    - MLKitBarcodeScanning
-    - MLKitCommon
-    - MLKitVision
-    - nanopb
-    - PromisesObjC
-    - SQLCipher
-    - ZIPFoundation
 
 EXTERNAL SOURCES:
   Capacitor:
     :path: "../../node_modules/@capacitor/ios"
   CapacitorApp:
     :path: "../../node_modules/@capacitor/app"
-  CapacitorCamera:
-    :path: "../../node_modules/@capacitor/camera"
-  CapacitorCommunitySqlite:
-    :path: "../../node_modules/@capacitor-community/sqlite"
   CapacitorCordova:
     :path: "../../node_modules/@capacitor/ios"
-  CapacitorFilesystem:
-    :path: "../../node_modules/@capacitor/filesystem"
-  CapacitorMlkitBarcodeScanning:
-    :path: "../../node_modules/@capacitor-mlkit/barcode-scanning"
-  CapacitorShare:
-    :path: "../../node_modules/@capacitor/share"
-  CapawesomeCapacitorFilePicker:
-    :path: "../../node_modules/@capawesome/capacitor-file-picker"
 
 SPEC CHECKSUMS:
-  Capacitor: c95400d761e376be9da6be5a05f226c0e865cebf
+  Capacitor: 05d35014f4425b0740fc8776481f6a369ad071bf
   CapacitorApp: e1e6b7d05e444d593ca16fd6d76f2b7c48b5aea7
-  CapacitorCamera: 9bc7b005d0e6f1d5f525b8137045b60cffffce79
-  CapacitorCommunitySqlite: 0299d20f4b00c2e6aa485a1d8932656753937b9b
-  CapacitorCordova: 8d93e14982f440181be7304aa9559ca631d77fff
-  CapacitorFilesystem: 59270a63c60836248812671aa3b15df673fbaf74
-  CapacitorMlkitBarcodeScanning: 7652be9c7922f39203a361de735d340ae37e134e
-  CapacitorShare: d2a742baec21c8f3b92b361a2fbd2401cdd8288e
-  CapawesomeCapacitorFilePicker: c40822f0a39f86855321943c7829d52bca7f01bd
-  GoogleDataTransport: 6c09b596d841063d76d4288cc2d2f42cc36e1e2a
-  GoogleMLKit: 90ba06e028795a50261f29500d238d6061538711
-  GoogleToolboxForMac: 8bef7c7c5cf7291c687cf5354f39f9db6399ad34
-  GoogleUtilities: ea963c370a38a8069cc5f7ba4ca849a60b6d7d15
-  GoogleUtilitiesComponents: 679b2c881db3b615a2777504623df6122dd20afe
-  GTMSessionFetcher: 5aea5ba6bd522a239e236100971f10cb71b96ab6
-  MLImage: 1824212150da33ef225fbd3dc49f184cf611046c
-  MLKitBarcodeScanning: 9cb0ec5ec65bbb5db31de4eba0a3289626beab4e
-  MLKitCommon: afcd11b6c0735066a0dde8b4bf2331f6197cbca2
-  MLKitVision: 90922bca854014a856f8b649d1f1f04f63fd9c79
-  nanopb: 438bc412db1928dac798aa6fd75726007be04262
-  PromisesObjC: f5707f49cb48b9636751c5b2e7d227e43fba9f47
-  SQLCipher: 31878d8ebd27e5c96db0b7cb695c96e9f8ad77da
-  ZIPFoundation: b8c29ea7ae353b309bc810586181fd073cb3312c
+  CapacitorCordova: b33e7f4aa4ed105dd43283acdd940964374a87d9
 
-PODFILE CHECKSUM: f987510f7383b04a1b09ea8472bdadcd88b6c924
+PODFILE CHECKSUM: 4233f5c5f414604460ff96d372542c311b0fb7a8
 
 COCOAPODS: 1.16.2

ios/App/Time Safari.xcodeproj/project.pbxproj

@@ -3,7 +3,7 @@
 	archiveVersion = 1;
 	classes = {
 	};
-	objectVersion = 54;
+	objectVersion = 48;
 	objects = {
 
 /* Begin PBXBuildFile section */
@@ -14,22 +14,22 @@
 		504EC30F1FED79650016851F /* Assets.xcassets in Resources */ = {isa = PBXBuildFile; fileRef = 504EC30E1FED79650016851F /* Assets.xcassets */; };
 		504EC3121FED79650016851F /* LaunchScreen.storyboard in Resources */ = {isa = PBXBuildFile; fileRef = 504EC3101FED79650016851F /* LaunchScreen.storyboard */; };
 		50B271D11FEDC1A000F3C39B /* public in Resources */ = {isa = PBXBuildFile; fileRef = 50B271D01FEDC1A000F3C39B /* public */; };
-		97EF2DC6FD76C3643D680B8D /* Pods_App.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 90DCAFB4D8948F7A50C13800 /* Pods_App.framework */; };
+		A084ECDBA7D38E1E42DFC39D /* Pods_App.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = AF277DCFFFF123FFC6DF26C7 /* Pods_App.framework */; };
 /* End PBXBuildFile section */
 
 /* Begin PBXFileReference section */
 		2FAD9762203C412B000D30F8 /* config.xml */ = {isa = PBXFileReference; lastKnownFileType = text.xml; path = config.xml; sourceTree = "<group>"; };
 		50379B222058CBB4000EE86E /* capacitor.config.json */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = text.json; path = capacitor.config.json; sourceTree = "<group>"; };
-		504EC3041FED79650016851F /* App.app */ = {isa = PBXFileReference; explicitFileType = wrapper.application; includeInIndex = 0; path = App.app; sourceTree = BUILT_PRODUCTS_DIR; };
+		504EC3041FED79650016851F /* Time Safari.app */ = {isa = PBXFileReference; explicitFileType = wrapper.application; includeInIndex = 0; path = "Time Safari.app"; sourceTree = BUILT_PRODUCTS_DIR; };
 		504EC3071FED79650016851F /* AppDelegate.swift */ = {isa = PBXFileReference; lastKnownFileType = sourcecode.swift; path = AppDelegate.swift; sourceTree = "<group>"; };
 		504EC30C1FED79650016851F /* Base */ = {isa = PBXFileReference; lastKnownFileType = file.storyboard; name = Base; path = Base.lproj/Main.storyboard; sourceTree = "<group>"; };
 		504EC30E1FED79650016851F /* Assets.xcassets */ = {isa = PBXFileReference; lastKnownFileType = folder.assetcatalog; path = Assets.xcassets; sourceTree = "<group>"; };
 		504EC3111FED79650016851F /* Base */ = {isa = PBXFileReference; lastKnownFileType = file.storyboard; name = Base; path = Base.lproj/LaunchScreen.storyboard; sourceTree = "<group>"; };
 		504EC3131FED79650016851F /* Info.plist */ = {isa = PBXFileReference; lastKnownFileType = text.plist.xml; path = Info.plist; sourceTree = "<group>"; };
 		50B271D01FEDC1A000F3C39B /* public */ = {isa = PBXFileReference; lastKnownFileType = folder; path = public; sourceTree = "<group>"; };
-		90DCAFB4D8948F7A50C13800 /* Pods_App.framework */ = {isa = PBXFileReference; explicitFileType = wrapper.framework; includeInIndex = 0; path = Pods_App.framework; sourceTree = BUILT_PRODUCTS_DIR; };
-		E2E9297D5D02C549106C77F9 /* Pods-App.release.xcconfig */ = {isa = PBXFileReference; includeInIndex = 1; lastKnownFileType = text.xcconfig; name = "Pods-App.release.xcconfig"; path = "Target Support Files/Pods-App/Pods-App.release.xcconfig"; sourceTree = "<group>"; };
-		EAEC6436E595F7CD3A1C9E96 /* Pods-App.debug.xcconfig */ = {isa = PBXFileReference; includeInIndex = 1; lastKnownFileType = text.xcconfig; name = "Pods-App.debug.xcconfig"; path = "Target Support Files/Pods-App/Pods-App.debug.xcconfig"; sourceTree = "<group>"; };
+		AF277DCFFFF123FFC6DF26C7 /* Pods_App.framework */ = {isa = PBXFileReference; explicitFileType = wrapper.framework; includeInIndex = 0; path = Pods_App.framework; sourceTree = BUILT_PRODUCTS_DIR; };
+		AF51FD2D460BCFE21FA515B2 /* Pods-App.release.xcconfig */ = {isa = PBXFileReference; includeInIndex = 1; lastKnownFileType = text.xcconfig; name = "Pods-App.release.xcconfig"; path = "Pods/Target Support Files/Pods-App/Pods-App.release.xcconfig"; sourceTree = "<group>"; };
+		FC68EB0AF532CFC21C3344DD /* Pods-App.debug.xcconfig */ = {isa = PBXFileReference; includeInIndex = 1; lastKnownFileType = text.xcconfig; name = "Pods-App.debug.xcconfig"; path = "Pods/Target Support Files/Pods-App/Pods-App.debug.xcconfig"; sourceTree = "<group>"; };
 /* End PBXFileReference section */
 
 /* Begin PBXFrameworksBuildPhase section */
@@ -37,17 +37,17 @@
 			isa = PBXFrameworksBuildPhase;
 			buildActionMask = 2147483647;
 			files = (
-				97EF2DC6FD76C3643D680B8D /* Pods_App.framework in Frameworks */,
+				A084ECDBA7D38E1E42DFC39D /* Pods_App.framework in Frameworks */,
 			);
 			runOnlyForDeploymentPostprocessing = 0;
 		};
 /* End PBXFrameworksBuildPhase section */
 
 /* Begin PBXGroup section */
-		4B546315E668C7A13939F417 /* Frameworks */ = {
+		27E2DDA53C4D2A4D1A88CE4A /* Frameworks */ = {
 			isa = PBXGroup;
 			children = (
-				90DCAFB4D8948F7A50C13800 /* Pods_App.framework */,
+				AF277DCFFFF123FFC6DF26C7 /* Pods_App.framework */,
 			);
 			name = Frameworks;
 			sourceTree = "<group>";
@@ -57,15 +57,15 @@
 			children = (
 				504EC3061FED79650016851F /* App */,
 				504EC3051FED79650016851F /* Products */,
-				BA325FFCDCE8D334E5C7AEBE /* Pods */,
-				4B546315E668C7A13939F417 /* Frameworks */,
+				7F8756D8B27F46E3366F6CEA /* Pods */,
+				27E2DDA53C4D2A4D1A88CE4A /* Frameworks */,
 			);
 			sourceTree = "<group>";
 		};
 		504EC3051FED79650016851F /* Products */ = {
 			isa = PBXGroup;
 			children = (
-				504EC3041FED79650016851F /* App.app */,
+				504EC3041FED79650016851F /* Time Safari.app */,
 			);
 			name = Products;
 			sourceTree = "<group>";
@@ -85,37 +85,35 @@
 			path = App;
 			sourceTree = "<group>";
 		};
-		BA325FFCDCE8D334E5C7AEBE /* Pods */ = {
+		7F8756D8B27F46E3366F6CEA /* Pods */ = {
 			isa = PBXGroup;
 			children = (
-				EAEC6436E595F7CD3A1C9E96 /* Pods-App.debug.xcconfig */,
-				E2E9297D5D02C549106C77F9 /* Pods-App.release.xcconfig */,
+				FC68EB0AF532CFC21C3344DD /* Pods-App.debug.xcconfig */,
+				AF51FD2D460BCFE21FA515B2 /* Pods-App.release.xcconfig */,
 			);
-			path = Pods;
+			name = Pods;
 			sourceTree = "<group>";
 		};
 /* End PBXGroup section */
 
 /* Begin PBXNativeTarget section */
-		504EC3031FED79650016851F /* App */ = {
+		504EC3031FED79650016851F /* Time Safari */ = {
 			isa = PBXNativeTarget;
-			buildConfigurationList = 504EC3161FED79650016851F /* Build configuration list for PBXNativeTarget "App" */;
+			buildConfigurationList = 504EC3161FED79650016851F /* Build configuration list for PBXNativeTarget "Time Safari" */;
 			buildPhases = (
-				92977BEA1068CC097A57FC77 /* [CP] Check Pods Manifest.lock */,
+				6634F4EFEBD30273BCE97C65 /* [CP] Check Pods Manifest.lock */,
 				504EC3001FED79650016851F /* Sources */,
 				504EC3011FED79650016851F /* Frameworks */,
 				504EC3021FED79650016851F /* Resources */,
-				012076E8FFE4BF260A79B034 /* Fix Privacy Manifest */,
-				3525031ED1C96EF4CF6E9959 /* [CP] Embed Pods Frameworks */,
-				96A7EF592DF3366D00084D51 /* Fix Privacy Manifest */,
+				9592DBEFFC6D2A0C8D5DEB22 /* [CP] Embed Pods Frameworks */,
 			);
 			buildRules = (
 			);
 			dependencies = (
 			);
-			name = App;
+			name = "Time Safari";
 			productName = App;
-			productReference = 504EC3041FED79650016851F /* App.app */;
+			productReference = 504EC3041FED79650016851F /* Time Safari.app */;
 			productType = "com.apple.product-type.application";
 		};
 /* End PBXNativeTarget section */
@@ -124,9 +122,8 @@
 		504EC2FC1FED79650016851F /* Project object */ = {
 			isa = PBXProject;
 			attributes = {
-				BuildIndependentTargetsInParallel = YES;
-				LastSwiftUpdateCheck = 920;
-				LastUpgradeCheck = 1630;
+				LastSwiftUpdateCheck = 0920;
+				LastUpgradeCheck = 0920;
 				TargetAttributes = {
 					504EC3031FED79650016851F = {
 						CreatedOnToolsVersion = 9.2;
@@ -135,7 +132,7 @@
 					};
 				};
 			};
-			buildConfigurationList = 504EC2FF1FED79650016851F /* Build configuration list for PBXProject "App" */;
+			buildConfigurationList = 504EC2FF1FED79650016851F /* Build configuration list for PBXProject "Time Safari" */;
 			compatibilityVersion = "Xcode 8.0";
 			developmentRegion = en;
 			hasScannedForEncodings = 0;
@@ -144,11 +141,13 @@
 				Base,
 			);
 			mainGroup = 504EC2FB1FED79650016851F;
+			packageReferences = (
+			);
 			productRefGroup = 504EC3051FED79650016851F /* Products */;
 			projectDirPath = "";
 			projectRoot = "";
 			targets = (
-				504EC3031FED79650016851F /* App */,
+				504EC3031FED79650016851F /* Time Safari */,
 			);
 		};
 /* End PBXProject section */
@@ -170,27 +169,25 @@
 /* End PBXResourcesBuildPhase section */
 
 /* Begin PBXShellScriptBuildPhase section */
-		012076E8FFE4BF260A79B034 /* Fix Privacy Manifest */ = {
+		6634F4EFEBD30273BCE97C65 /* [CP] Check Pods Manifest.lock */ = {
 			isa = PBXShellScriptBuildPhase;
-			alwaysOutOfDate = 1;
 			buildActionMask = 2147483647;
 			files = (
 			);
-			inputFileListPaths = (
-			);
 			inputPaths = (
+				"${PODS_PODFILE_DIR_PATH}/Podfile.lock",
+				"${PODS_ROOT}/Manifest.lock",
 			);
-			name = "Fix Privacy Manifest";
-			outputFileListPaths = (
-			);
+			name = "[CP] Check Pods Manifest.lock";
 			outputPaths = (
+				"$(DERIVED_FILE_DIR)/Pods-App-checkManifestLockResult.txt",
 			);
 			runOnlyForDeploymentPostprocessing = 0;
 			shellPath = /bin/sh;
-			shellScript = "\"${PROJECT_DIR}/app_privacy_manifest_fixer/fixer.sh\" \n";
+			shellScript = "diff \"${PODS_PODFILE_DIR_PATH}/Podfile.lock\" \"${PODS_ROOT}/Manifest.lock\" > /dev/null\nif [ $? != 0 ] ; then\n    # print error to STDERR\n    echo \"error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.\" >&2\n    exit 1\nfi\n# This output is used by Xcode 'outputs' to avoid re-running this script phase.\necho \"SUCCESS\" > \"${SCRIPT_OUTPUT_FILE_0}\"\n";
 			showEnvVarsInLog = 0;
 		};
-		3525031ED1C96EF4CF6E9959 /* [CP] Embed Pods Frameworks */ = {
+		9592DBEFFC6D2A0C8D5DEB22 /* [CP] Embed Pods Frameworks */ = {
 			isa = PBXShellScriptBuildPhase;
 			buildActionMask = 2147483647;
 			files = (
@@ -205,47 +202,6 @@
 			shellScript = "\"${PODS_ROOT}/Target Support Files/Pods-App/Pods-App-frameworks.sh\"\n";
 			showEnvVarsInLog = 0;
 		};
-		92977BEA1068CC097A57FC77 /* [CP] Check Pods Manifest.lock */ = {
-			isa = PBXShellScriptBuildPhase;
-			buildActionMask = 2147483647;
-			files = (
-			);
-			inputFileListPaths = (
-			);
-			inputPaths = (
-				"${PODS_PODFILE_DIR_PATH}/Podfile.lock",
-				"${PODS_ROOT}/Manifest.lock",
-			);
-			name = "[CP] Check Pods Manifest.lock";
-			outputFileListPaths = (
-			);
-			outputPaths = (
-				"$(DERIVED_FILE_DIR)/Pods-App-checkManifestLockResult.txt",
-			);
-			runOnlyForDeploymentPostprocessing = 0;
-			shellPath = /bin/sh;
-			shellScript = "diff \"${PODS_PODFILE_DIR_PATH}/Podfile.lock\" \"${PODS_ROOT}/Manifest.lock\" > /dev/null\nif [ $? != 0 ] ; then\n    # print error to STDERR\n    echo \"error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.\" >&2\n    exit 1\nfi\n# This output is used by Xcode 'outputs' to avoid re-running this script phase.\necho \"SUCCESS\" > \"${SCRIPT_OUTPUT_FILE_0}\"\n";
-			showEnvVarsInLog = 0;
-		};
-		96A7EF592DF3366D00084D51 /* Fix Privacy Manifest */ = {
-			isa = PBXShellScriptBuildPhase;
-			alwaysOutOfDate = 1;
-			buildActionMask = 2147483647;
-			files = (
-			);
-			inputFileListPaths = (
-			);
-			inputPaths = (
-			);
-			name = "Fix Privacy Manifest";
-			outputFileListPaths = (
-			);
-			outputPaths = (
-			);
-			runOnlyForDeploymentPostprocessing = 0;
-			shellPath = /bin/sh;
-			shellScript = "$PROJECT_DIR/app_privacy_manifest_fixer/fixer.sh\n";
-		};
 /* End PBXShellScriptBuildPhase section */
 
 /* Begin PBXSourcesBuildPhase section */
@@ -293,7 +249,6 @@
 				CLANG_WARN_BOOL_CONVERSION = YES;
 				CLANG_WARN_COMMA = YES;
 				CLANG_WARN_CONSTANT_CONVERSION = YES;
-				CLANG_WARN_DEPRECATED_OBJC_IMPLEMENTATIONS = YES;
 				CLANG_WARN_DIRECT_OBJC_ISA_USAGE = YES_ERROR;
 				CLANG_WARN_DOCUMENTATION_COMMENTS = YES;
 				CLANG_WARN_EMPTY_BODY = YES;
@@ -301,10 +256,8 @@
 				CLANG_WARN_INFINITE_RECURSION = YES;
 				CLANG_WARN_INT_CONVERSION = YES;
 				CLANG_WARN_NON_LITERAL_NULL_CONVERSION = YES;
-				CLANG_WARN_OBJC_IMPLICIT_RETAIN_SELF = YES;
 				CLANG_WARN_OBJC_LITERAL_CONVERSION = YES;
 				CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
-				CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER = YES;
 				CLANG_WARN_RANGE_LOOP_ANALYSIS = YES;
 				CLANG_WARN_STRICT_PROTOTYPES = YES;
 				CLANG_WARN_SUSPICIOUS_MOVE = YES;
@@ -314,10 +267,8 @@
 				CODE_SIGN_IDENTITY = "iPhone Developer";
 				COPY_PHASE_STRIP = NO;
 				DEBUG_INFORMATION_FORMAT = dwarf;
-				DEVELOPMENT_TEAM = 7XVXYPEQYJ;
 				ENABLE_STRICT_OBJC_MSGSEND = YES;
 				ENABLE_TESTABILITY = YES;
-				ENABLE_USER_SCRIPT_SANDBOXING = YES;
 				GCC_C_LANGUAGE_STANDARD = gnu11;
 				GCC_DYNAMIC_NO_PIC = NO;
 				GCC_NO_COMMON_BLOCKS = YES;
@@ -355,7 +306,6 @@
 				CLANG_WARN_BOOL_CONVERSION = YES;
 				CLANG_WARN_COMMA = YES;
 				CLANG_WARN_CONSTANT_CONVERSION = YES;
-				CLANG_WARN_DEPRECATED_OBJC_IMPLEMENTATIONS = YES;
 				CLANG_WARN_DIRECT_OBJC_ISA_USAGE = YES_ERROR;
 				CLANG_WARN_DOCUMENTATION_COMMENTS = YES;
 				CLANG_WARN_EMPTY_BODY = YES;
@@ -363,10 +313,8 @@
 				CLANG_WARN_INFINITE_RECURSION = YES;
 				CLANG_WARN_INT_CONVERSION = YES;
 				CLANG_WARN_NON_LITERAL_NULL_CONVERSION = YES;
-				CLANG_WARN_OBJC_IMPLICIT_RETAIN_SELF = YES;
 				CLANG_WARN_OBJC_LITERAL_CONVERSION = YES;
 				CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
-				CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER = YES;
 				CLANG_WARN_RANGE_LOOP_ANALYSIS = YES;
 				CLANG_WARN_STRICT_PROTOTYPES = YES;
 				CLANG_WARN_SUSPICIOUS_MOVE = YES;
@@ -376,10 +324,8 @@
 				CODE_SIGN_IDENTITY = "iPhone Developer";
 				COPY_PHASE_STRIP = NO;
 				DEBUG_INFORMATION_FORMAT = "dwarf-with-dsym";
-				DEVELOPMENT_TEAM = 7XVXYPEQYJ;
 				ENABLE_NS_ASSERTIONS = NO;
 				ENABLE_STRICT_OBJC_MSGSEND = YES;
-				ENABLE_USER_SCRIPT_SANDBOXING = YES;
 				GCC_C_LANGUAGE_STANDARD = gnu11;
 				GCC_NO_COMMON_BLOCKS = YES;
 				GCC_WARN_64_TO_32_BIT_CONVERSION = YES;
@@ -391,69 +337,60 @@
 				IPHONEOS_DEPLOYMENT_TARGET = 13.0;
 				MTL_ENABLE_DEBUG_INFO = NO;
 				SDKROOT = iphoneos;
-				SWIFT_COMPILATION_MODE = wholemodule;
-				SWIFT_OPTIMIZATION_LEVEL = "-O";
+				SWIFT_OPTIMIZATION_LEVEL = "-Owholemodule";
 				VALIDATE_PRODUCT = YES;
 			};
 			name = Release;
 		};
 		504EC3171FED79650016851F /* Debug */ = {
 			isa = XCBuildConfiguration;
-			baseConfigurationReference = EAEC6436E595F7CD3A1C9E96 /* Pods-App.debug.xcconfig */;
+			baseConfigurationReference = FC68EB0AF532CFC21C3344DD /* Pods-App.debug.xcconfig */;
 			buildSettings = {
 				ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
 				CODE_SIGN_STYLE = Automatic;
-				CURRENT_PROJECT_VERSION = 26;
+				CURRENT_PROJECT_VERSION = 1;
 				DEVELOPMENT_TEAM = GM3FS5JQPH;
-				ENABLE_APP_SANDBOX = NO;
-				ENABLE_USER_SCRIPT_SANDBOXING = NO;
 				INFOPLIST_FILE = App/Info.plist;
+				INFOPLIST_KEY_CFBundleDisplayName = "Time Safari";
+				INFOPLIST_KEY_LSApplicationCategoryType = "public.app-category.social-networking";
 				IPHONEOS_DEPLOYMENT_TARGET = 13.0;
-				LD_RUNPATH_SEARCH_PATHS = (
-					"$(inherited)",
-					"@executable_path/Frameworks",
-				);
-				MARKETING_VERSION = 0.5.1;
+				LD_RUNPATH_SEARCH_PATHS = "$(inherited) @executable_path/Frameworks";
+				MARKETING_VERSION = 1.0;
 				OTHER_SWIFT_FLAGS = "$(inherited) \"-D\" \"COCOAPODS\" \"-DDEBUG\"";
 				PRODUCT_BUNDLE_IDENTIFIER = app.timesafari;
 				PRODUCT_NAME = "$(TARGET_NAME)";
 				SWIFT_ACTIVE_COMPILATION_CONDITIONS = DEBUG;
 				SWIFT_VERSION = 5.0;
 				TARGETED_DEVICE_FAMILY = "1,2";
-				VERSIONING_SYSTEM = "apple-generic";
 			};
 			name = Debug;
 		};
 		504EC3181FED79650016851F /* Release */ = {
 			isa = XCBuildConfiguration;
-			baseConfigurationReference = E2E9297D5D02C549106C77F9 /* Pods-App.release.xcconfig */;
+			baseConfigurationReference = AF51FD2D460BCFE21FA515B2 /* Pods-App.release.xcconfig */;
 			buildSettings = {
 				ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
 				CODE_SIGN_STYLE = Automatic;
-				CURRENT_PROJECT_VERSION = 26;
+				CURRENT_PROJECT_VERSION = 1;
 				DEVELOPMENT_TEAM = GM3FS5JQPH;
-				ENABLE_APP_SANDBOX = NO;
-				ENABLE_USER_SCRIPT_SANDBOXING = NO;
 				INFOPLIST_FILE = App/Info.plist;
+				INFOPLIST_KEY_CFBundleDisplayName = "Time Safari";
+				INFOPLIST_KEY_LSApplicationCategoryType = "public.app-category.social-networking";
 				IPHONEOS_DEPLOYMENT_TARGET = 13.0;
-				LD_RUNPATH_SEARCH_PATHS = (
-					"$(inherited)",
-					"@executable_path/Frameworks",
-				);
-				MARKETING_VERSION = 0.5.1;
+				LD_RUNPATH_SEARCH_PATHS = "$(inherited) @executable_path/Frameworks";
+				MARKETING_VERSION = 1.0;
 				PRODUCT_BUNDLE_IDENTIFIER = app.timesafari;
 				PRODUCT_NAME = "$(TARGET_NAME)";
 				SWIFT_ACTIVE_COMPILATION_CONDITIONS = "";
 				SWIFT_VERSION = 5.0;
 				TARGETED_DEVICE_FAMILY = "1,2";
-				VERSIONING_SYSTEM = "apple-generic";
 			};
 			name = Release;
 		};
 /* End XCBuildConfiguration section */
 
 /* Begin XCConfigurationList section */
-		504EC2FF1FED79650016851F /* Build configuration list for PBXProject "App" */ = {
+		504EC2FF1FED79650016851F /* Build configuration list for PBXProject "Time Safari" */ = {
 			isa = XCConfigurationList;
 			buildConfigurations = (
 				504EC3141FED79650016851F /* Debug */,
@@ -462,7 +399,7 @@
 			defaultConfigurationIsVisible = 0;
 			defaultConfigurationName = Release;
 		};
-		504EC3161FED79650016851F /* Build configuration list for PBXNativeTarget "App" */ = {
+		504EC3161FED79650016851F /* Build configuration list for PBXNativeTarget "Time Safari" */ = {
 			isa = XCConfigurationList;
 			buildConfigurations = (
 				504EC3171FED79650016851F /* Debug */,

ios/App/app_privacy_manifest_fixer/.gitignore

@@ -1,5 +0,0 @@
-# macOS
-.DS_Store
-
-# Build
-/Build/

ios/App/app_privacy_manifest_fixer/CHANGELOG.md

@@ -1,58 +0,0 @@
-## 1.4.1
-- Fix macOS app re-signing issue.
-- Automatically enable Hardened Runtime in macOS codesign.
-- Add clean script.
-
-## 1.4.0
-- Support for macOS app ([#9](https://github.com/crasowas/app_privacy_manifest_fixer/issues/9)).
-
-## 1.3.11
-- Fix install issue by skipping `PBXAggregateTarget` ([#4](https://github.com/crasowas/app_privacy_manifest_fixer/issues/4)).
-
-## 1.3.10
-- Fix app re-signing issue.
-- Enhance Build Phases script robustness.
-
-## 1.3.9
-- Add log file output.
-
-## 1.3.8
-- Add version info to privacy access report.
-- Remove empty tables from privacy access report.
-
-## 1.3.7
-- Enhance API symbols analysis with strings tool.
-- Improve performance of API usage analysis.
-
-## 1.3.5
-- Fix issue with inaccurate privacy manifest search.
-- Disable dependency analysis to force the script to run on every build.
-- Add placeholder for privacy access report.
-- Update build output directory naming convention.
-- Add examples for privacy access report.
-
-## 1.3.0
-- Add privacy access report generation.
-
-## 1.2.3
-- Fix issue with relative path parameter.
-- Add support for all application targets.
-
-## 1.2.1
-- Fix backup issue with empty user templates directory.
-
-## 1.2.0
-- Add uninstall script.
-
-## 1.1.2
-- Remove `Templates/.gitignore` to track `UserTemplates`.
-- Fix incorrect use of `App.xcprivacy` template in `App.framework`.
-
-## 1.1.0
-- Add logs for latest release fetch failure.
-- Fix issue with converting published time to local time.
-- Disable showing environment variables in the build log.
-- Add `--install-builds-only` command line option.
-
-## 1.0.0
-- Initial version.