5 ms·
>IoT devices [are] hard to prototype, generally low-margin, expensive to bring to market, and very expensive to scale. Just ask Fitbit. Or Jawbone. Or Juicero.
by komali2 9y ago
>IoT devices [are] hard to prototype, generally low-margin, expensive to bring to market, and very expensive to scale. Just ask Fitbit. Or Jawbone. Or Juicero. Or HTC.
I feel like this is the public's idea of "iot," while I've learned after a year of working for an iot stack provider that the real "internet of things" explosion is found in places nobody looks except the procurement guys - the stadium lights, the refrigerators, the factory doors, etc. Small, single-minded decided sending one or two bytes of data, spread en masse through an industrial area.
- leggomylibro 9y agoYeah, it seems like you could replace 'IoT' with 'physical product.' Sounds like the author has been living in the land of hand-waved 9-figure growth estimates for a bit too long.
- erikb 9y agoNo you cannot. A brick is also a physical product. But it doesn't communicate. There needs to be software and technology involved, and more than one object needs to talk via a network.
- leggomylibro 9y agoThat's true, but a brick still requires a sophisticated set of knowledge which we accept to be public domain by this point, after a few thousand years. You need to know how to make and fire clay, what sorts of additives can help, how to package and ship them en masse... There are a lot of problems involved in bricks. OSHA once categorized bricks as hazardous materials (don't breathe the dust when grinding them). We've just gotten really good at dealing with those problems because of how useful bricks are and how easy it is to teach people about making them. Anecdotally, I once took an archaeology course in college, and we had a guest speaker come in who knew how to do flint-knapping[1]. Like, prehistoric toolmaking out of volcanic rocks. I'll bet you'd run into some real hurtles trying to market an obsidian knife today, if you didn't have experience in that area. [1]: https://en.wikipedia.org/wiki/Knapping https://en.wikipedia.org/wiki/Knapping
- TeMPOraL 9y agoI think the GP's point is that software is not the hard part when you're dealing with physical products, connected or not...
- erikb 9y agoWell who means what is really hard to discuss at this point. The article's author wants to point out that the hardware part must be so cheap that you can't make any profit in that area any more. But you still need to get it right, otherwise you can't sell anything. Komali doesn't disagree with that point, but adds another. That most of IoT is actually not in the consumer area but in the industry area where people don't see it but the scale in terms of item numbers might be much bigger. Also a good point. Then leggomylibro points out that you could replace "IoT" with "physical product", which may or may not imply that hardware is the hard part in IoT. In the literally interpretation I disagree with the equal sign there, because a brick is not "IoT". There shouldn't be much to say about htis. IoT _is_ about the communication, right? Considering your interpretation of his statement, that the hardware is the hard part in IoT, makes me wonder how you define hard part. The physical important parts like chips are quite well understood I believe (not an expert though) and we churn these out in the millions each year and they mostly do their job. The point where these chips actually need to be connected to physical I/O and software, these are horribly underdeveloped areas. There is low amount of skilled people, low amount of debugging, low amount of standards. If that's the area you are talking about I agree. However if we talk business, we also need to talk money. And while you have one or two suicidal hardware architect on such a project, you probably have 50-100 software developers, who will use open-source plugins, libraries, operating systems, which again are each developed by 50-100 developers. So the whole cost of software is margins higher than the costs of developing the hardware. And that factor is growing towards the software side on a daily basis. The hardware will grow more and more to standardized processing units (GPUs, SoCs, touchdisplays for I/O) and the main activity will happen in more and more in software. So considering that part I have to say nope, software is the harder part (to finance, to develop, to finish) here.
- TeMPOraL 9y agoWhat I mean by physical part being the harder here is that it's much slower and more expensive to iterate on. You can make a lot of changes to software within a single day, for free (sans programmer time), and deploy them to all your customers. With physical items, you usually need to fab a new version for each significant change to test it, which is a time-consuming and expensive process. This is not something electronics-specific, this applies just as much to a new brick design. This is a qualitative difference that makes physical product design an expensive process - you need to get all the things right before you start shipping; you can't just patch things after you deploy. But, as the article correctly points out, ultimately the manufacturing of a correctly designed batch of a physical item is cheap. Which means it's hard to make profit, especially if you spent all that money iterating in your lab, and then someone just reverse-engineers your final design and starts pumping out copies. In case of IoT - common processing and communication chips are cheap and easy to get. Electrical engineering is hard and expensive, product design is hard and expensive, and - compared to that - software is cheap, because all IoT companies are doing is bog standard cloud-based CRUD. (If they make the software part needlessly complicated for themselves, that's another problem, but it's endemic to this industry anyway.)
- Animats 9y agoThat's called "machine to machine communication", or "M2M", by the companies who do that. Much of it is still over pager networks. There are hundreds of thousands of industrial HVAC systems, quietly sending "Inside temp 72, outside temp 87, compressor 1 on/OK/2421 operating hours, compressor 2 off/OK/3423 operating hours, coolant pressure OK, water level in chiller OK, city water pressure OK..." back to a maintenance service.
- ilamont 9y agoExactly. Google "Industrial IoT" or "Industrie 4.0" and it's pretty clear that some major changes are happening with IoT, far away from consumer gadgetry like Nest and an IP-enabled light bulb.
- TeMPOraL 9y agoHaving worked with some companies in the field, I feel "Industry 4.0" is just about the same level of marketing fad as "Sharing Economy". Something useful will eventually appear there, but my impression is that there's lot of papering over crappy tech with sales being done, and people are jockeying for position of being the platform provider, who sucks everyone else into their SaaS offering. In a way, it doesn't look that different from consumer IoT, which is probably why people think calling it IIoT is a good idea (instead of trying to separate themselves away from the accumulated bullshit IoT is). Not the kind of revolution I fought for.
- contingencies 9y agoIoT devices [are] hard to prototype Here in Shenzhen, I would say no. They are cheap as chips. I have multiple friends doing consumer IoT devices (lots of BLE) with single-dimensional backgrounds (often software) who have been able to iterate through multiple prototypes and produce concepts within months. The chief problems for IoT products IMHO are marketing and replicability (low security for initial investment). The fact that hardware is expensive to tackle in SV just means SV is badly positioned in this sector, not that it's inherently difficult or expensive. BTW, we just had the Hacker Trip to China (by Noisebridge founder Mitch Altman) roll through town here.
- spiffytech 9y agoHow does a software person get that far with hardware that fast?
- contingencies 9y agoIt's really not that hard. A bit of electronics comprehension is the only requirement, and there are many helpful people about and hackerspaces for those who are new. For example this Wednesday my favourite hackerspace https://lab0x0.com/ https://lab0x0.com/ is offering a free introductory course in English for people totally new to arduino. There are tonnes of books and resources online, and a friendly 24x7 WeChat group for live help. A shopping trip to buy sensors and bits in town here can be completed in half a day and under $100 (including soldering equipment), two days of hacking and anyone motivated will be on top of the basics.
- leggomylibro 9y agoI mean, even outside of Shenzhen, if you want bluetooth the NRF52832 has fantastic hardware layout/design documentation and a frickin' Cortex-M0+ processor for core logic and communicating with the BTLE stack. The ESP32 has wifi and bluetooth and has dealt with all that FCC crap (but uses a weird MCU core.) Etc, etc. Living next door to a few factories probably reduces your iteration times from weeks to days, but IMHO - and maybe this is the 'H' part, I'm still learning - the time that you as an individual wind up spending on design and figuring out software issues are pretty sizable, even compared to a fortnight for a nice 2-4 layer PCB. Either way, we are certainly living in a wonderful time for rapid prototyping. Dropping the 'IoT' tag, embedded systems are super super exciting in all kinds of areas; telecommunications are just one of those.