How to test an IOT-enabled smart-kitchen concept without building the product?

@philipsnyder @jaithakur Gotcha, so you're talking exactly the 'Amazon Dash' concept. TL;DR - Few years ago Amazon launched the concept of "Dash Buttons" which allowed the user to re-order some predetermined product (though you could customise the buttons to whatever product you wanted). e.g. you're running out of laundry detergent, you tap the 'Tide' button, and it automatically orders it for you As an extension of that concept, to eliminate even the button pressing and automate the restocking, Amazon came out with a concept of "inventory sensors" where the various products could self report and be added to the cart - e.g. a washing machine automatically reordering detergent, or a coffee pod system automatically reordering more coffee pods. https://web.archive.org/web/2019... They managed to get quite a few very large companies to sign up for that service, but eventually just merged parts of it into the bigger Alexa ecosystem where I haven't seen it gain much traction while killing off the Dash Buttons entirely. Fundamentally it's not a bad concept, but the biggest use case challenge that you have to overcome is the same one that is faced by any of the diet tracking apps such as MyFitnessPal, Lifesum, PlateJoy etc. The challenge being that for the app to be truly useful, they do require a significant amount of input from the user. So in your case, the challenge is that of convenience vs cost - e.g. 1) these sensors/containers are bought by the user, which is then expected to transfer some product to that container, open the app, input the type of product they just placed in it, specify at what threshold they want it to be reordered etc --- more affordable but far more effort to the user which at some point gets to be more effort than it's worth 2) disposable sensors which are built directly into the products being sold - which is marginally more convenient for customers (though they still have to pair/authenticate every product) while it also adds a ton of overhead cost for the manufacturers while creating more ewaste afterwards. I think it would be a very interesting problem to solve, but the challenge isn't the making of an MVP/demo. The challenge comes when you start breaking down the hundreds of scenarios that a user will encounter where the costs/effort required starts increasing in orders of magnitude which is why so far every company, including those who poured tens of millions of dollars into it, haven't been able to come up with a real solution to the problem.