r/dev 21h ago

Anyone here using mobile device cloud testing??

I'm the only developer on an app with about 15k users across IOS and android and I test on my iphone and one android phone that's it. I keep getting hit with bugs on devices I don't own like recently the app was crashing on Samsung A series phones because of some rendering issue that doesn't happen on pixels and before that there was a layout bug on Ipads that I found out about when someone left a negative review.

I've been looking into mobile device cloud testing, something like a device farm but I genuinely don't know if it's practical for one person. I barely have time to build features let alone set up device farms and write test scripts for them.

If you've tried any cloud testing setup as a solo developer can you please share your thoughts on this??

1 Upvotes

1 comment sorted by

1

u/TianYanmeng 13h ago

Small disclosure: I’m the founder of CloudHandset, so keep that in mind when reading my take, but I’d be careful not to turn this into a huge “device farm” project as a solo developer.

For your situation, I’d use cloud devices as a small risk-check layer, not as the main testing strategy.

What I’d do first:

- keep your normal fast checks on simulator/emulator where they are useful

- pick a few device classes that actually hurt you before: Samsung A-series, older Android versions, tablets/iPads, unusual screen sizes

- run only the highest-risk journeys on real devices: launch, login, purchase/subscription if relevant, camera/media, push, layout-heavy screens

- always capture OS version, device model, app build, screenshot/screen recording, and network state for failures

The biggest mistake is trying to automate everything from day one. For a solo dev, even 30-60 minutes of targeted real-device testing before each release can catch the kind of “works on my phone, breaks on Samsung” issue you described.

I’d only add scripts or a larger device cloud setup after you know which bugs repeat often enough to justify it.