In DC we also have JUMP (tho this Uber integration seems to be SF only), in addition to ofo, spin, mobike & limebike. And in my experience JUMP doesn't suffer from the majority of the issues the other dockless providers do. Their bikes are much higher quality and lock to something. This quality comes at a price, so the provider is more invested in bikes remaining in operation, whereas the other providers' bikes are so cheap that the companies treat them as disposable leading to most of the problems.
Re: vans -- dockless providers do this too (at least in DC, where they're required to)
Edit: and since this is HN, I've gotta point out that JUMP is also the only dockless operator in DC with an easy to use & publicly accessible API.
I'm not sure what the full authenticated API[0] can do, maybe the sort of integration Uber did is possible. But with the open data APIs make it easy to find all bikes currently available in the system. I've used them to add JUMP to my bike finder webapp[2] and build a little service to send myself notification of where the nearest JUMP bike is in the morning[3] because they don't yet have huge coverage in DC (working on porting this from single user + pushover to a PWA using web push).
Re: vans -- dockless providers do this too (at least in DC, where they're required to)
Edit: and since this is HN, I've gotta point out that JUMP is also the only dockless operator in DC with an easy to use & publicly accessible API.