"and While techy guys like you or me were fixing issues on low quality products, the whole world learned how to enjoy their high quality phones/tablets with thousnads of apps poured in the market,"
yep, that right there. I still get a little excited installing linux on a machine knowing that I'm going to have all these little problems to reasearch and fix. It is actually part of the fun. However, that just isn't practical on something that I need to be able to whip out and work on.
Like said, after using both Android and iOS right from the start, as a mobile software developer, my first feeling was to say "Great article Caleb, that's exactly how things go, Android is buggy and iOS is nicely polished and working flawlessly".
However the comparison between the two is a bit stretched, and the results are a bit irrelevant, here's why:
Android is an open source platform. Google doesn't impose major guidelines to manufacturers so the total freedom results both in a lot of creativity (we see android running on endless devices of all kinds) but also a lot of fragmentation and problems when porting applications (the screen size is a minor one, as there are a lot more)
On the other hand, Apple carefully designes just a few hardware devices, carefully controls the production and then is also able to control in every details the way their final product works and feels. Do we want that? Maybe we do: as said, iOS will preform flawlessly and all applications including the OS will show little bugs and issues.
But... we love hacks, don't we Caleb? Having the platform open source not only allows us to hack into the OS and extend it to our needs, but we are even free to correct the so-called bugs and push updates if we want so.
You'll never get this freedom in the iOS world. So we get it simple and nice, or we get in complex but then we must be prepared to face the consequences: in a more complex system there can be bugs, issues and glitches but at least it's open source and we have a chance of changing something.
The ones which worked perfectly for me, were all made by Apple. S3, when I got it from my carrier, was loaded with bloatware and made me want to stomp on it. You always have to tune this & that to make it work properly. All the 5 Apple devices I had, combined crashed on me, may be less than 10-20 times in 3-4 years. While S3 alone crashed on me atleast 200 times in the 8 months I used it. Though I like the several added features in Android(swype, digitiser pen, larger screen), If I want something reliable I will always pick Apple.
I totally hear you Caleb, wearing the IT admin hat as the main or occasional responsibility.
I too never liked the idea of beiing controlled by an application (iTune) and not being able to manage my files, HW resources, etc.,and since it was not cool to use an end-user type device from Apple, I avoided that for a long time.
However, after some years of super successful market for iPhone, iPad, and other iThings, I came to belive that Apple is doing somethin right and one of them is to deliver what is advertised\promised in their product. I know many average iPhone, ipad end-users from all ages and background whom their only problem that I have heard they had were caused by physical or water damages and everything is so simple that they can all manage it without any deep technical knowledge.
and While techy guys like you or me were fixing issues on low quality products, the whole world learned how to enjoy their high quality phones/tablets with thousnads of apps poured in the market, hope to hear your feedback again after you adopted to your new ipad.
I really just can't afford to spend all my time making it work and researching the workarounds. I have gotten a lot of responses like... you could root it and then load a custom bluetooth driver to see if that helps... or you could hunt down and buy this one keyboard which we've heard still works...
nope, give me the product that does what it says it will do on the box. thanks.
I spent many of the PC years fighting with BSOD issues, driver issues, etc., and was often envious of those who bought the expensive desktop machine from that other company and claimed that it always "just works." Back then I was willing to invest a fair amount of my time troubleshooting & fixing software issues because I convinced myself that the money I saved was worth some of my time.
But when the tablet era arrived, I bought one from that other company -- primarily because they happened to be out there first -- and the thing has worked flawlessly ever since. I think I have gotten spoiled now, and have no desire to go back to hackerware, or uninstalling & reinstalling software to see if I can get it to work again, or delving into the nuances of BT or WiFi simply because the thing randomly stops connecting to a network to which it used to connect.
The hardware is first rate in all of these devices and it's rare to encounter an actual hardware problem. But until I'm convinced that software is as universally robust among the various mobile platforms, I'm content to stick with something that "just works."
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.