Cross-Platform Desktop Backup Tool (One-Way Upload)
Budget: $750 – $1,500 USD
We are building a cloud platform designed for DJs, producers, and artists to store, organize, and share large music libraries.
We are seeking an experienced desktop developer to create a simple and reliable desktop backup tool that automatically uploads files from a user’s computer to their cloud account.
### Important Project Details:
**This project is a one-way upload only:**
- Local to Cloud only
- No automatic downloads
- No two-way sync
- No conflict resolution
- No file deletions propagated back to the local system
The feature should be presented as:
**"Backup your desktop music/files automatically to the cloud."**
Phase 1 is intentionally basic, focusing on high-value features to keep costs low and execution clean.
### Architecture Expectations:
The solution should consist of:
- A CLI-based background sync engine that handles:
- Folder watching
- Chunked and resumable uploads
- Retry logic
- Logging
- Upload queue management
- A very lightweight desktop UI wrapper that:
- Controls the CLI engine
- Provides basic status updates and controls
- Runs at system startup
- Does NOT expose a terminal to the user
Users will only interact with the UI.
### What We Need (Phase 1 – MVP):
The desktop tool (for Windows and macOS) should:
- Run automatically at system startup (in the background)
- Authenticate securely with our web app API
- Allow users to select one or more folders to back up
- Watch selected folders for changes
- Automatically upload new or modified files
- Support very large files (e.g., WAV, AIFF)
- Utilize chunked and resumable uploads
- Handle unreliable internet connections gracefully
- Allow for pause and resume functionality
- Provide basic upload status and logs
- Upload files directly to cloud storage (not routed through the web app)
### UI Expectations:
The UI should be intentionally minimal and may include:
- Login screen
- Folder selection
- Backup on/off toggle
- Upload progress indicator
- Status text (Idle / Uploading / Paused)
- Pause/Resume controls
- Basic settings (start on login, optional bandwidth limit)
Design polish is NOT a priority; reliability is.
### Technology (Open to Suggestions):
We are open to using:
- Go, Node.js, or similar for the CLI engine
- Electron or Tauri for the UI wrapper
- Reusing proven libraries/tools where appropriate
We value developers who:
- Understand why CLI-based engines are ideal for this type of task
- Can clearly explain trade-offs
- Avoid overengineering
- Build stable, reliable systems
### What This Project Is NOT:
- A Dropbox-style sync client
- A two-way synchronization tool
- A real-time collaboration application
- An enterprise desktop app
- A highly polished consumer UI
### Budget and Engagement:
We are looking for a cost-effective solution and are open to either fixed-price or milestone-based contracts. Phase 1 should be lean and affordable. We prefer to establish a long-term relationship and want to grow this project from basic to advanced over time with the right candidate.
Please be upfront about:
- What you would build first
- What features you would intentionally skip
- What might incur additional costs later
- How you would structure future upgrades
### Ideal Candidate:
You are a good fit if you:
- Have built desktop tools for both Windows and macOS
- Have experience with backup, sync, or upload tools
- Have worked with large file uploads and resumable transfers
- Understand CLI-based architectures
- Are comfortable delivering simple MVPs
- Communicate clearly and honestly
**Bonus experience (not required):**
- Backup utilities
- Media or audio tools
- CLI tooling
- Early-stage startup products
### How to Apply:
Please include the following in your application:
- Your recommended approach for the CLI engine and UI wrapper
- The technologies you would use and your rationale
- A rough cost range for Phase 1
- A timeline estimate
- Examples of similar work
Generic or copy-paste proposals will be ignored.
### Why Work With Us:
- Clear project scope
- A real product with a roadmap
- No unrealistic expectations
- Long-term potential
- We value execution over buzzwords
### Final Note:
Please do not propose two-way sync or advanced features in Phase 1. Simplicity and reliability are more important than many features.
We are seeking an experienced desktop developer to create a simple and reliable desktop backup tool that automatically uploads files from a user’s computer to their cloud account.
### Important Project Details:
**This project is a one-way upload only:**
- Local to Cloud only
- No automatic downloads
- No two-way sync
- No conflict resolution
- No file deletions propagated back to the local system
The feature should be presented as:
**"Backup your desktop music/files automatically to the cloud."**
Phase 1 is intentionally basic, focusing on high-value features to keep costs low and execution clean.
### Architecture Expectations:
The solution should consist of:
- A CLI-based background sync engine that handles:
- Folder watching
- Chunked and resumable uploads
- Retry logic
- Logging
- Upload queue management
- A very lightweight desktop UI wrapper that:
- Controls the CLI engine
- Provides basic status updates and controls
- Runs at system startup
- Does NOT expose a terminal to the user
Users will only interact with the UI.
### What We Need (Phase 1 – MVP):
The desktop tool (for Windows and macOS) should:
- Run automatically at system startup (in the background)
- Authenticate securely with our web app API
- Allow users to select one or more folders to back up
- Watch selected folders for changes
- Automatically upload new or modified files
- Support very large files (e.g., WAV, AIFF)
- Utilize chunked and resumable uploads
- Handle unreliable internet connections gracefully
- Allow for pause and resume functionality
- Provide basic upload status and logs
- Upload files directly to cloud storage (not routed through the web app)
### UI Expectations:
The UI should be intentionally minimal and may include:
- Login screen
- Folder selection
- Backup on/off toggle
- Upload progress indicator
- Status text (Idle / Uploading / Paused)
- Pause/Resume controls
- Basic settings (start on login, optional bandwidth limit)
Design polish is NOT a priority; reliability is.
### Technology (Open to Suggestions):
We are open to using:
- Go, Node.js, or similar for the CLI engine
- Electron or Tauri for the UI wrapper
- Reusing proven libraries/tools where appropriate
We value developers who:
- Understand why CLI-based engines are ideal for this type of task
- Can clearly explain trade-offs
- Avoid overengineering
- Build stable, reliable systems
### What This Project Is NOT:
- A Dropbox-style sync client
- A two-way synchronization tool
- A real-time collaboration application
- An enterprise desktop app
- A highly polished consumer UI
### Budget and Engagement:
We are looking for a cost-effective solution and are open to either fixed-price or milestone-based contracts. Phase 1 should be lean and affordable. We prefer to establish a long-term relationship and want to grow this project from basic to advanced over time with the right candidate.
Please be upfront about:
- What you would build first
- What features you would intentionally skip
- What might incur additional costs later
- How you would structure future upgrades
### Ideal Candidate:
You are a good fit if you:
- Have built desktop tools for both Windows and macOS
- Have experience with backup, sync, or upload tools
- Have worked with large file uploads and resumable transfers
- Understand CLI-based architectures
- Are comfortable delivering simple MVPs
- Communicate clearly and honestly
**Bonus experience (not required):**
- Backup utilities
- Media or audio tools
- CLI tooling
- Early-stage startup products
### How to Apply:
Please include the following in your application:
- Your recommended approach for the CLI engine and UI wrapper
- The technologies you would use and your rationale
- A rough cost range for Phase 1
- A timeline estimate
- Examples of similar work
Generic or copy-paste proposals will be ignored.
### Why Work With Us:
- Clear project scope
- A real product with a roadmap
- No unrealistic expectations
- Long-term potential
- We value execution over buzzwords
### Final Note:
Please do not propose two-way sync or advanced features in Phase 1. Simplicity and reliability are more important than many features.