Electron Snapchat Multiview Automation

Заказчик: AI | Опубликовано: 14.01.2026
Бюджет: 250 $

I have an Electron-based desktop app that can spin up between one and ten embedded Snapchat Web sessions side-by-side in a resizable grid. Each pane should look and feel like a self-contained “mini Snapchat,” complete with its own controls and live status read-outs so I can see at a glance which accounts are logged in, idle, sending, or throttled. Core workflow • Manual proxy entry per session. When I open a new pane I should be able to paste an IP:PORT (with optional user:pass) and have that proxy applied only to that webview. • Friend list import per account via a simple TXT or CSV upload. The app must parse the file, queue the names, and keep track of which ones have been processed. • Automated actions: add friends from the queue and send photo snaps on a configurable delay that I can tweak in milliseconds or seconds. The routine needs to run for hours without leaking memory, desyncing, or triggering Snapchat’s rate limits more than absolutely necessary. • Persistent settings so grid layout, proxies, delay values, and any unfinished queues survive a restart. Deliverables 1. Cross-platform Electron app (Windows/macOS at minimum) packaged and ready to install. 2. Source code with clear instructions for building, plus a short README that documents the main modules and the environment variables. 3. Robust error handling: automatic re-login if a session drops, visible warnings if a proxy fails, and graceful retries on failed friend requests or snap sends. 4. A simple in-app log viewer and an exportable logfile for long-run diagnostics. Acceptance criteria – With ten sessions running, CPU and RAM usage remain within reasonable desktop limits and or work well on server hardware. – Friend add & snap send success rate stays above 95 % during a continuous 6-hour test. – Switching proxies or importing a new list never freezes or crashes the UI. I’m aiming to have the first usable build within 60 days and the polished, production-ready version by day 90. Let’s discuss any technical constraints you foresee in hitting that schedule. I have the base coded already , and you can see all the UI for every panel.