My experience with Android has been similar. The operating system is buggy and the hardware (I have a Nexus phone, Goog designed - Samsung made) is unreliable. My 2 year contract is running out next month and I cannot wait to replace this phone with a Nokia 920 or 1020. Android seems to be worth about as much as it costs. I will never buy Apple, not because of their quality but because I am fundamentally opposed to their philosophy of closed systems (both sw and hw).
I thought it was just my luck and I'm doing the same as you by going away from android for the same reasons.
At first I thought it was because I did the same as you, a free nook color which I then rooted with Gingerbread and then after frustration with GB I then went to jelly bean and I thought that just maybe I was expecting too much from the poor old nook.
Fortunately I had a data card for Gingerbread and jelly bean which along with the Nook made it simple to test apps on the 2 Os's, GB or JB.
With GB and JB I had almost the same issues but with different apps peforming fine under one OS while not performing on the different Os, what worked fine with Ginger Bread didn't work on Jelly bean and vice versa.
Then the screen lockups and constant rebooting, the touch screen not working with one app but then working fine on another os with the same app but then another part of an app not working and then constantly tweaking the darn thing and really holding back from wanting to use it as a skeet shooting target.
To top the frustrations off the wife picked up a dedicated androind tablet with the latest and greatest JB and it has the same issues but with differnt apps so whether its's running gingerbread, jellybean the little GREEN ALIEN is just way too buggy for me.
And of course my number 1 complaint being was that I could find only one browser that worked with flash but then the touch screen was screwy and it would constantly reboot in the middle of something while when the same browser was running under a different OS it didn't work at all with flash even though each browser claimed flash support.
To get around this problem with flash videos and the browsers I found myself booting into Nook color mode with my tablet and actually found the native nook mode really supported a lot more over wifi and much more stable than any of the android OS's.
Well, like anything else, the answer is yes and no.
No, because ideally, the Android ecosystem should be imposing rules that vendors should follow: for example, every vendor has a different camera, but from the app perspective it's just a camera that the app conencts though OS API and gets the details through that API. If the vendor wants to add completely new hardware (like a light saber or phaser ;) to the device, then it calls Google to request addition of new device type to the baseline and let Google define the API.
Yes, well of course the vendors would like to corner the market and supply their apps that work only on their hardware. How to prevent that is probably job for Google.
That isn't a horrible solution, as you said, it worked for microsoft. I wonder how different that is from what they're doing now?
Then, if the vendors are supplying their own hardware driver sets, what happens to the apps? Would this make the marketplace worse? Would it end up devolving back to each vendor offering their own apps?
I agree. Apple has control over their products, but that limits the offerings. Microsoft was software company with the huge hardware fragmentation but they controlled the OS and vendors supplied the drivers (in my mind good concept, crappy implementation).
Google should provide OS and ability for vendors to add hardware specific functions in a defined and secure way. How to do this, I don't know (I'm not even close to smart enough :).
I'm not smart enough to have a solution to the hardware fragmentation issue. I just know it causes a lack of continuity between experiences and that detracts from the entire product. If I had a clever solution I'd be pitching it to google right now.
I suppose it was software, I wouldn't call everything there bloatware especially for my home theatre system.
Kies is worse than iTunes, if something like that is possible.
We should be able to streamline Android (I even recompiled one for 7" Samsung but never had time to take out stuff that is obviously bloatware and clean up the kernel), but it seems that is not the priority for Google - the answer is put more CPU power and hope for the best.
In my mind, Google should close Android for phone vendors and allow ONLY app additions to the platform. Right now, everyone is free to add as much crap as they want and sell it to us.
I tend to write within the content management system I'm using if I'm writing for the web. Unfortunately, the online editors don't always render in mobile devices. Other than that I tend to write in plain text all the time. Gdocs covers my needs generally.
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.