I don't mean to bash your company at all here, so I'm sorry if this comes off that way. I was excited when I saw your indoor SDK, but it's too simplistic and not realistic enough for the production apps we have and are building (walking around and mapping every single room in a hospital is untenable). All 3 Estimote beacons are dead, and they all died around the same time (one in super conservative mode, one in what should be a normal use case, and then one in max power mode). The beacons my company received from you guys must have been out of the norm then. Hold the phone between you and the beacon and get a decent signal, then turn 180 degrees so that you are between the phone and the beacon. But they die too quickly, and don't provide granular signal data. And that's only because they don't have batteries. The only beacons that don't are RadBeacons USB sticks that plug into wall outlets. Did I mention power yet? All of the beacons we started with around 9 months ago have dead batteries. Using beacons for granular location-aware uses might as well go out the window if you're looking for accurate and precise readings around ~1-3ft. Speaking of indoor navigation, you need a ton of points to do it well (whether that's beacons or wifi routers, you decide). I recommend as the only solution that got close to what we needed (though it's still pretty darn immature). Indoor navigation that relies on iBeacons only is going to shoot you in the foot. Nobody likes things they didn't ask for getting sent to their phone. Estimated battery life was estimated very poorly. Some of my findings over the last 9 months: As an iOS developer who has spent the last 9 months making beacon enabled things for my employer, I personally think beacons are shit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |