I’m a mobile developer and my desk has always been a mess because of all of the devices I need to manually test on scattered about.
This weekend I decided to finally organize my desk. To help do that I looked up some solutions for phone organization and decided instead of buying an organizer I can just design and print my own.
Used a caliper to measure the dimensions of the devices, wrote down an approximate ideal size of the organizer based on that.
Created this design in opencad after relearning the tool (haven’t used it in a few months).
Then got it printed in petg.
And voila it works. I’m pretty happy the first prototype worked as the print time was around 4 hours so I really didn’t want to have to iterate too many times.
I don’t develop for mobile outside reactive websites
I just wanted to ask why exactly you need all those and why emulators don’t work well enough?
Emulators cannot re-create all the dumb bullshit and quirks that phone manufacturers put in there these days
Sounds like an android problem
Because interfacing with all the sensors, dealing with battery aging underclocking, and other practical usage scenarios just aren’t applicable to iphones?
Correct
Every device in that pile (aside from the pixel 1 and pixel 7 which were my old daily drivers turned test device) was purposefully purchased because we got a report/logs of a bug on that specific device and had no way of fixing the issue unless we had the actual device.
This isn’t the full stack of devices I have but these are the devices we’ve had problems with in the past and what I frequently test with these days.
Not every phone is as capable as an iPhone Pro Ludicrous. If you don’t want your software to suck balls, test with slower devices.
And Throttle the network because not every user has fiber and WiFi 7 on a network colocated with the dev server