Setup Splitly Base Application

[RajkumarGara]

Summary:
Initialize the Splitly application — a fast, reactive, and cross-platform expense-sharing tool built with Meteor, Bootstrap, and MongoDB/IndexedDB. This ticket covers the setup of the base architecture, core data handling, and navigation structure.

Tech Stack:

• Frontend: Meteor + Bootstrap
• Database: MongoDB (cloud persistence) & IndexedDB (offline/local storage)
• Data Format: JSON (primary structure for data storage and exchange)

Features to Implement:

1. App Initialization

   • Create a new Meteor project named Splitly.
   • Integrate Bootstrap for responsive and mobile-first UI.
   • Configure Meteor’s reactive data system.

2. Database Setup

   • Connect MongoDB for cloud persistence.
   • Implement IndexedDB for local/offline caching.
   • Ensure synchronization between IndexedDB and MongoDB.

3. Data Models (JSON-based)

   • Define base JSON structures for:
     • User – name, contact info, saved preferences.
     • Bill – date, items, total, participants, and split details.
     • Item – item name, price, assigned users, split type (equal/custom).
     • Expense Summary – calculated totals per user.

4. Routing & Pages

   • / → Dashboard / Home (overview of recent bills).
   • /new → New Bill Upload/Scan Page.
   • /history → List of previously saved bills with date and total.
   • /analysis → Expense Analysis with charts and graphs.

5. UI Components

   • Create a top navigation bar for routing between pages.
   • Add placeholder sections for each feature.
   • Maintain clean Bootstrap layout and responsive design.

6. Reactive Functionality

   • Enable Meteor’s real-time updates for data changes.
   • Ensure UI updates automatically when bills or user data are modified.

7. Configuration Files

   • Use JSON or YAML for app configuration (e.g., API keys, environment variables).

Deliverables:

• Working Meteor app with Bootstrap styling.
• MongoDB + IndexedDB integration.
• Defined JSON data models.
• Functional routing between Dashboard, New Bill, History, and Analysis pages.
• Verified reactivity and data flow.