Three days of Splashtop shows how stable the system is
A few days ago, my monitor had a stroke. That left me with using only Splashtop on my iPad to access my desktop computer for the last 3 days, until I eventually thought I’d give repairing the monitor another shot, stripped it down to there was nothing left to disassemble, put it back together, turned it on, and was welcomed with the “Acer” logo. Me being able to fix a monitor with nothing but dumb luck is not the point here however, the point is how stable Splashtop has been for me the last few days.
The Splashtop app has been running on my AC connected iPad 2 about 16 hours a day for these three days, which is likely more than what it was intended to do. With it running constantly for that long, even very rare bugs and mishaps will eventually happen, except that they haven’t. The thing has been rock solid, pumping the screen and audio to my iPad for hours on end without a hitch. I’ve mostly used it for video, which tends to be where you notice the least bit of response delay because you’re not interacting with the screen much and the bandwidth isn’t the problem. Even for other uses though, it’s been rock solid and as good as I could ever hope for for a wireless touch screen.
These last three days has given me more faith in Splashtop than ever before. It’s an app I love, and one that I thing truly makes tablets more useful than many people realize. It pains me to talk to people who have never heard of Splashtop or any other form of remote computer control, because often it’s something they would have used if they knew it existed. After saving my butt for three days, I thought a public pat on its back was the least I could do.
