Public Projects

Build a mobile app: I want to build an expense tracker app named as SpenSense this app will track my daily expenses on what i am spending like groceries travelling week ends trip and electricity and furniture and all the other things and also i want to keep a category of savings i will set a budget for savings so that amounnt i ll not be spending until its an emergency and i need the app to be well looked the complete theme should be green and white the first look of the screen should have the name of my app and the logo and down there will be proceed to login button or bar then the login user interface then its upto u

A Nigerian custom made shoe app, that not only finding customers for shoe makers in nigeria but balso making payment and delivery easy. likewise making delivery fee less expensive

build me an ios storage cleaner app

Recreate my Android app from scratch called CHECKIN. Build it with Kotlin + Jetpack Compose + Material 3, CameraX, ML Kit, Supabase, Room, Coroutines, ViewModels and Repository architecture. The app is a real attendance management system with two separate roles: 1. STUDENT 2. LECTURER IMPORTANT: Build REAL functionality, not UI prototypes, simulations, fake data, random attendance, or placeholder camera/biometric features. CORE FEATURES: • Email/password authentication, verification, password reset and persistent login. • Lecturer can create an institution using: - School name - Unique permanent institution code • Students and lecturers can join an existing institution using the code. • Institution data must be stored in Supabase and work across different devices. • Never use hardcoded/demo institutions or randomly assign users to institutions. • Use one canonical institution ID for all users, courses, sessions and attendance. DATABASE: Create Supabase tables for: - profiles - institutions - institution_members - courses - attendance_sessions - attendance_records Use proper foreign keys, unique constraints and Row Level Security. LECTURER: - Create/manage courses - Create attendance sessions - Generate QR attendance - Start live attendance - Use a REAL CameraX camera to detect multiple people - Show detected people count - Support biometric/face verification where implemented - Support GPS/geofence attendance - View attendance records and statistics - Export attendance STUDENT: - View institution and courses - See active attendance sessions from Supabase - Scan REAL QR codes using CameraX - Use REAL face/biometric verification - Use GPS verification when required - View attendance history and statistics CROSS-DEVICE FLOW: Lecturer creates session → Supabase → Student device retrieves session → Student verifies using QR/face/GPS → AttendanceRecord created → Supabase → Lecturer sees updated attendance. A student from another institution MUST NOT see or join the session. GPS must only be required when the session actually requires GPS. CAMERA: Use real CameraX frame processing. Do not simulate faces, counts or attendance. Do not create fake biometric matches. OFFLINE: Use Room as a local cache. Queue attendance when offline. Sync with Supabase when internet returns. Never report a failed sync as successful. UI: Create a professional modern Material 3 interface with separate Student and Lecturer dashboards, loading states, errors, empty states, permissions and proper navigation. IMPORTANT: Do not claim a feature is complete unless it is actually implemented and tested. Before completion: - Build the project - Fix compilation errors - Verify Supabase/database integration - Verify authentication - Verify institution joining - Verify cross-device sessions - Verify QR - Verify GPS - Verify biometric/face functionality - Verify lecturer multi-person camera - Verify attendance recording - Verify offline sync - Verify security/RLS At the end, give me a short report showing each major feature as: IMPLEMENTED / PARTIALLY IMPLEMENTED / NOT IMPLEMENTED and mention the exact files/components involved.

Give me a website where I saw baseball card sports cards and electronics size game consoles computers and laptops

AURA LAB — PRODUCTION E-COMMERCE DEVELOPMENT You are the lead software architect, senior full-stack engineer, UI/UX designer, e-commerce engineer and QA engineer for AURA LAB. Treat this as a REAL COMMERCIAL PROJECT. Modify my EXISTING application. Do not create a mockup, demo, fake checkout, fake orders or fake tracking. BRAND AURA LAB Tagline: A FRAGRANCE THAT LINGERS. Premium fragrance brand. Market: Pakistan. Primary payment: Cash on Delivery. Style: luxury, minimal, sophisticated, modern, mysterious, premium and editorial. CURRENT HOSTING The existing website is deployed on Google Cloud Run. IMPORTANT: Never hard-code an old domain. Never use auralab.pages.dev unless it is actually the active production domain. Never assume auralab.pk exists. All customer-generated URLs must use the current runtime origin, preferably: window.location.origin Example: ${window.location.origin}/track-order?order=AURA-XXXXXX&phone=XXXXXXXXXXX ================================================== CORE CUSTOMER FLOW ================================================== HOME → SHOP → PRODUCT → SELECT SIZE → ADD TO CART / BUY NOW → CHECKOUT → CONFIRM ORDER → FIRESTORE → REAL ORDER ID → ORDER CONFIRMATION → TRACK ORDER BUSINESS FLOW: CUSTOMER ORDER → FIRESTORE → ADMIN DASHBOARD → REAL-TIME ORDER UPDATE → ADMIN STATUS UPDATE → CUSTOMER TRACKING UPDATE Everything must use real persistent data. ================================================== TECHNOLOGY ================================================== Use the existing architecture wherever practical. Frontend: React + TypeScript Backend: Existing Node.js/server architecture Database: Firebase Firestore Hosting: Google Cloud Run Admin: Secure authentication and authorization Do not unnecessarily rewrite working parts of the application. ================================================== DATABASE ================================================== Firestore is the authoritative source of truth. Collections: orders products customers Orders must NOT depend on localStorage. localStorage may only be used for temporary cart/cache functionality. Orders must survive: - refresh - browser restart - different browser - different device - customer leaving the site - admin refresh ================================================== ORDER DATA ================================================== Each order should contain: orderId customerName phone email address city items productId productName size quantity unitPrice subtotal deliveryFee total paymentMethod orderDate createdAt updatedAt status customerNotes Statuses: CONFIRMED PROCESSING SHIPPED OUT_FOR_DELIVERY DELIVERED CANCELLED ================================================== CRITICAL ORDER CONFIRMATION ================================================== When customer clicks CONFIRM ORDER: 1. Validate all checkout fields. 2. Validate cart. 3. Validate product availability. 4. Prevent duplicate submission. 5. Generate unique customer-friendly ID such as AURA-735462. 6. Save complete order to Firestore. 7. Wait for successful Firestore response. 8. Verify the order can be retrieved. 9. Set status to CONFIRMED. 10. ONLY THEN show ORDER CONFIRMED. 11. ONLY THEN enable WhatsApp. If Firestore fails, never show success. Show: "Your order could not be confirmed. Please try again." Never silently lose an order. ================================================== ORDER CONFIRMATION PAGE ================================================== Show: ✓ ORDER CONFIRMED Thank you for choosing AURA LAB. Order Number: AURA-XXXXXX Show: - Products - Sizes - Quantities - Prices - Subtotal - Delivery - Total - Payment method - Delivery address - Current status Buttons: TRACK MY ORDER CONTINUE SHOPPING ================================================== CUSTOMER TRACKING ================================================== Route: /track-order Support: /track-order?order=AURA-XXXXXX&phone=03142087801 Tracking must retrieve the REAL order from Firestore. Do not use hard-coded sample orders. Use order number + phone, or another secure existing verification method. Display: - Order ID - Customer - Products - Sizes - Quantity - Total - Payment method - Order date - Address - Current status Timeline: CONFIRMED ↓ PROCESSING ↓ SHIPPED ↓ OUT FOR DELIVERY ↓ DELIVERED Highlight the current status. If order does not exist or verification fails, show a clear error. ================================================== OLD TRACKING BUG ================================================== The previous application generated links like: https://auralab.pages.dev/track-order?order=AURA-735462&phone=03142087801 This must be FIXED. Search the entire project for: auralab.pages.dev Remove incorrect references. Tracking links must always use the CURRENT production origin. Also check: - WhatsApp links - order records - redirects - frontend constants - backend constants - environment variables - confirmation pages ================================================== WHATSAPP ================================================== WhatsApp is optional. It must NOT be required to place an order. After Firestore successfully saves the order, provide: SEND ORDER TO WHATSAPP Message should include: AURA LAB Order ID Customer Products Sizes Quantity Total Delivery information Tracking URL Tracking URL must use the current production origin. ================================================== ADMIN ================================================== Routes: /admin /admin/orders /admin/products Use secure authentication. Never expose admin passwords or secrets in frontend code. Admin must see REAL Firestore orders. Display: Order ID Customer Phone Email Products Sizes Quantity Subtotal Delivery Total Payment method Date Status Admin can change: CONFIRMED PROCESSING SHIPPED OUT FOR DELIVERY DELIVERED CANCELLED When admin changes status, the customer tracking page must show the updated status. Use Firestore realtime listeners where appropriate so new orders appear without manual refresh. New-order notification: 🔔 NEW ORDER Order: AURA-XXXXXX Customer: Customer Name Total: Rs. X,XXX Do not repeatedly notify the same order after refresh. ================================================== SECURITY ================================================== Never expose: - private API keys - Firebase Admin credentials - server secrets - database credentials Customers may only perform allowed customer operations. Admin operations require authorization. Validate and sanitize all customer input. Prevent: - duplicate orders - unauthorized status changes - unauthorized product changes - unauthorized order access ================================================== CLOUD RUN ================================================== Keep the existing Cloud Run deployment architecture. Do not make the application dependent on: auralab.pk or auralab.pages.dev Ensure: - production build works - server starts - routes work - Firestore works - orders persist - admin works - tracking works - WhatsApp works - mobile works IMPORTANT: Before changing files, inspect the existing project and understand its current architecture. Reuse working components instead of unnecessarily replacing them. Do not claim completion until the critical order lifecycle is actually tested.

PROMPT: Create a polished six-page digital and printable daily planner The planner should feel like a handcrafted autumn stationery collection: warm, tactile, calm, cozy, and highly functional. Use an original hand-painted watercolor and gouache art direction inspired by fall botanicals and cozy seasonal objects. The artwork must be newly created—not copied from a reference image. VISUAL DIRECTION - Warm cream and parchment paper backgrounds - Burnt orange, terracotta, ochre, chestnut brown, muted olive, sage green, and subtle plum accents - Soft paper texture, delicate borders, dashed writing rules, restrained shadows, and rounded paper panels - Elegant editorial serif typography for headings - Clean, highly legible sans-serif typography for labels - Occasional handwritten-style accent text - Refined and cozy rather than childish, cartoonish, or overly decorative - Generous whitespace and clearly defined writing areas - Accessible contrast and an organized visual hierarchy - No emojis - No prefilled personal answers, example tasks, meetings, habits, books, goals, or reflection responses CORE FUNCTIONAL REQUIREMENT This must be a genuinely blank write-in planner. Every section should begin empty and allow the person to write, type, or check items off. Use blank ruled fields, empty checkboxes, unselected trackers, empty tables, and subtle instructional placeholders only. Create six separate but visually coordinated pages

створи програму для перегляду рецептів, планування, розрахунку, широкий функціонал, мінімум той шо представлений у файлі, враховуй всі нюанси, до найдрібніших, адаптивна програма, різні вийнятки і додаткові функції, фільтри і максимально можлива реалізація. дозволені зміни всього контенту, збереження всієї детальної інформації та відкриття файлу як json а також завантаження вже закладеної в коді бази. також сам проаналізуй і зроби повноцінний html із гарним інтерфейсом, вхідною сторінкою і т. д. ось файл: https://docs.google.com/spreadsheets/d/1liUaTtL7j6p2ryjT_NDJ8fQPaYaOn3BP/edit?usp=sharing&ouid=114984269946464786206&rtpof=true&sd=true

build a landing page based on https://dealbyethan.gay/collections/gigo-underwear . make all the buttons/links link to that page and https://dealbyethan.gay and other relevant pages.

https://cr-remover.in/ Mujy asi website bana kar do without changing

make me a website about Allstate Sales Agent Office Address: 4997 Highway 7, Unit 9, Markham, ON L3R 1N1, Direct Phone: +1 289-307-0053, Agency Phone: +1 289-806-2438, Languages Spoken: English, Mandarin, Cantonese, and Taiwanese

need to build a small website for a chartered accountant firm from india objective: online presence + SEO + visibility and lead gen name and branding has been decided need to showcase: services, founder profile, lead gen form / contact us