Yes, Yoto! It’s not just for (kids) audiobooks, they have music cards too. And you can upload your own MP3s to their blank cards, or use it as a Bluetooth speaker.
Yoto! looks interesting. My nephew got a Voxblock [0] for Christmas and loves it.
Practical and easy. It's not interactive and you can buy an wide collection of audio books (made with recycled cardboard) and listen to it with headphones
At my work, we use an internal config store developed by another team for app config management, versioning and audit history.
It’s a bit flaky so we’ve been looking to replace it but don’t want to spend the company’s money building it. We’ve been looking but have not really found anything OSS.
We’re looking for:
- store text/binary documents
- full audit history of document versions
- get/put like api to retrieve/replace documents
- GUI to explore history/documents
- easily deplorable on Windows (ideally without an app server)
Hmm, I’m actually working on a project that’s hopefully not too orthogonal to your need but could overlap on a couple of points above - https://www.deltatrail.io. Basically changelog as a service (which may cover the audit trail history you mention). Our logic is that most shops don’t want to build something like this from scratch. Take a look if you’d like. We are still in beta and experimenting with market so let me know if there is a potential overlap and we can fill in the gaps where needed. Reachable at Ryan at Deltatrail.io.
Vault is for secret management. If you are just looking at a key value based store or a service discovery tool, you might want to have a look at consul by Hashicorp.
I estimate it takes 20 mins to buy an ice cream in Japan. If it takes "half a day" that's (charitably) 12x (8-hour days), or (uncharitably) 24x (16-hour days).
If I estimate a month to build your feature and it takes me a year or two, you're not going to be very happy...
I believe the GP is talking about the trend of adverts for the exact product you just viewed/bought on the exact store following you around the Internet for a few days.
e.g. you bought a blue striped t-shirt from H&M and it is continually advertised to you by H&M for a few days.
Surely refresh is just kill for web-apps? The app's state is discarded, the code is reloaded and it re-requests the data. I don't see the differentiation Tim is implying.
One requires the push of a convenient button already within the workflow of the app; the other requires knowing how to force close an app, or at any rate losing your flow.
I recently tried to use Google Maps offline mode while abroad. I had a local SIM but limited coverage and limited data allowance. I also had created some saved maps via Google My Maps with pins of points of interest. It exposed a lot of bugs in the app. Off the top of my head:
- Without coverage, the offline maps work well and show the pins from my saved maps. Search also worked well.
- As soon as I came back into coverage or wifi, it would close the saved maps and then not load them again if the connection was poor.
- Also, if there is a connection, it constantly tries to load address/photos/reviews for your pins and refuses to show the name you've given them. Not much use in a national park.
- When online with a poor connection, search doesn't work and doesn't fall back to the offline maps.
- When routing, you can't add a via point when offline as it refuses to use the offline search index.
- Disabling mobile data usage for the app just caused chaos.
All in all, it was a maddening experience. It's a classic case of Google offering more features, but with less polish. I used to use other pinning apps for holiday planning, but they've all shut down or stopped working properly (Pindrop, Rego). I was hoping the increased integration between Google Maps and Google My Maps would solve the issue but unfortunately it's very buggy right now.
Of course, Apple doesn't really have offline maps so, although I use Apple Maps as my main maps app, they score poorly here. Of course, this fits with their traditional approach of no feature is better than a badly implemented feature.
