Android cloud backup app scaled to 800K users with no team

When cloud backups were not yet standard on Android, Arth Patel built Contacts Backup, one of the platform’s first apps to let users backup their contacts to the cloud, long before Google’s native solutions were reliable or widely adopted. Created entirely solo using PHP and shared hosting, the app prioritized simplicity and trust. It grew to serve over 800,000 users, backed up more than 100 million contacts, and even earned informal recommendations from T-Mobile support teams.

How Arth Patel built one of the first Android cloud backup apps, and scaled it to 800K users with no team

In this Q&A, Arth shares how he built and scaled the app without a team, personally supported users, and designed for real-world failure. He also reflects on how those early lessons translated to his work on Instagram Direct and cross-app account switching at Meta. Now a recognized expert in mobile infrastructure, Arth was recently invited to speak at MobileSoft 2025 on Conquering iOS PREQ Challenges. His story is a reminder that thoughtful, resilient engineering often begins with solving one real problem well.

ADM: What led you to build this app when cloud backup wasn’t mainstream?

Patel: It started with a simple pain point I saw everywhere, people losing their phones and, with them, years of contacts. Back in 2012, Android didn’t offer reliable cloud sync for all devices. Even when it was available, many users didn’t have it enabled or didn’t know it existed. The only real alternative was exporting to SD cards or manually re-entering everything. I wanted to create something that just worked, an app that backed up and restored contacts reliably, with minimal effort. That was the motivation behind Contacts Backup.

ADM: How did you scale the app’s backend as a solo developer with limited infrastructure?

Patel: I didn’t have cloud credits or a DevOps team. I had shared hosting and PHP. I built a simple backend that accepted contacts as JSON, wrote them to disk, and returned success or error codes. Every decision was driven by constraints. I had to keep it lean, fault-tolerant, and easy to monitor. I wrote defensive logic to handle upload failures and malformed input, and I monitored logs manually. It sounds primitive today, but it worked. And it taught me how to think about reliability from day one, even without enterprise tools.

ADM: What design decisions helped the app remain intuitive for non-technical users?

Patel: The app required users to sign up with a username and password, and there was a basic onboarding screen that explained how the backup and restore process worked. But once logged in, users stayed authenticated, and the core experience was stripped down to two main buttons: Backup and Restore. No deep menus, no distractions. I designed it with the mindset that someone opening the app might be stressed or worried about losing data, so it had to be quick, clear, and calming.

ADM: How did you build and maintain user trust without branding or marketing?

Patel: I focused on respect and transparency. I personally assisted users via email support if they faced any issues, and I have hundreds of thank-you emails from people I helped recover their contacts. I also handled feedback directly and wrote detailed, honest release notes. I never added ads or tried to monetize user data. I did ask for app reviews, but only after users had used the app a few times. The prompt was subtle and skippable. That small gesture, combined with the app’s reliability, helped users feel like it was built for them, not for me. And that built long-term trust.

ADM: What did you learn from organic growth and informal T-Mobile endorsements?

Patel: That solving a real problem well is more powerful than any growth strategy. I started getting emails from users saying T-Mobile reps had recommended the app when customers lost phones. I hadn’t pitched it to them or run ads. It just spread because it worked. That experience taught me that people will advocate for tools that make their lives easier, especially when they fill a real gap. You can’t fake that kind of word-of-mouth.

ADM: How have those lessons translated into your work at Meta and beyond?

Patel: They’ve shaped how I approach engineering at every level. At Meta, I’ve worked on infrastructure powering Instagram Direct and the account switcher between Facebook and Instagram, features used by hundreds of millions of people. But the fundamentals are the same. Build systems that are clear, reliable, and respectful of the user. The experience of creating something from scratch, scaling it solo, and learning directly from users gave me a strong foundation. It reminded me that fast is good, but thoughtful and stable is better, especially at scale.

ADM: Would you build the same app today, and how would you approach it differently?

Patel: Definitely. The core problem, giving people control over their data, still matters. Today, the data is already encrypted, but I’d add features like multi-device sync and support for exporting backups to cloud drives like Google Drive or iCloud. I’d also design the UI with accessibility in mind and provide better insights into what data has been backed up and when. But the philosophy wouldn’t change. Don’t overwhelm the user, earn their trust, and make sure the product does what it promises, every single time.

ADM: What advice do you have for solo developers building infrastructure-heavy apps?

Patel: Don’t get caught up in buzzwords or over-engineering. You don’t need the perfect tech stack to build something meaningful. Focus on the user problem, start simple, and make sure it works well under real-world conditions. Expect things to break and build for that. And when you ask for a user’s time or trust, honor it. That’s what will make your app memorable, even if no one knows your name.

About Arth Patel

Arth Patel is an expert mobile developer with over 12 years of experience building high-scale apps across social, enterprise, and consumer domains. At Meta, he worked on Instagram Direct infrastructure and helped develop the account switching feature between Facebook and Instagram. He previously created one of Android’s first cloud-based contact backup apps, which served over 800,000 users and managed more than 100 million contacts. Arth has also contributed to MATLAB Mobile at MathWorks, worked on enterprise solutions at IBM, and co-founded two travel startups. He is passionate about building simple, reliable mobile experiences and frequently shares insights on app performance and debugging. In 2025, he was invited to speak at MobileSoft on Conquering iOS PREQ Challenges.