Thanks I'm glad you like it. I will take you up on that and get you on email.
As you can tell we are adding an intelligence layer above notification providers. That will certainly help reduce the friction in on-boarding for co's like roost. Much like Segment.io did for analytics companies.
Having a closer integration with you guys would be a great benefit.
We designed it as a REST API so it can work across all platforms mobile, web and desktop.
The API is super easy so it's simple to integrate within most apps. As time goes on we will be adding client libraries for common platforms, languages and frameworks to make integration even easier.
The naming is certainly something I have issues with. I haven't really spent any time thinking about how else to express it but I don't think I will be short of ideas when I do.
In terms of what kind of talent it will attract I have no idea. For me personally I think with the type of issues we want to deal with, diversity is key. You need talent as much as you just need a different point of view.
It's great that you have been thinking about doing something at your university. What other things have you experienced so far ?
I completely agree, I think there are many ways you could do things on a longer term basis. I think the idea of the "startup weekend" style event has a couple of benefits in this context.
1. It's a good way to try it and see what happens and learn so you can learn what to improve in the format.
2. It helps gain momentum because you're only requesting a small amount of initial time investment from people.
3. One of the key points I wanted to stress was the ability to have organisations on hand to help fill in knowledge gaps about the realties of the situation data etc, and also be able be actively involved in the process. I think it's easier to get them involved in that capacity for one weekend. Then build on there involvement after they see the value etc.
I think you're dead on with on with your intuitions. I find QA a problem because on a traditional production line QA is a very defined process.
However in software what is QA the UI, interaction, API, backend code ?
More to the point do I really need QA ? As a Startup is QA not a part of our core design and iteration process as we try to achieve "product market fit" ?
That's exactly the direction we where going would you mind looking at our extension. You don't have to use it just maybe read and watch the demo vid. I would love to get your thoughts on it.
So do you think that's what's more important it's not that bookmarks are wrong it's that the UX is terrible ? Or is that reading stuff later is actually what you want to do most of the time with bookmarks ?
I think the opposite you're exactly the person worth paying attention to :)
I think most people like the idea of being "free" from hoarding. because it clutters the mind. I guess the thing with bookmarks is that they need to disappear after either an action or a certain amount of time has passed since they where last used/created.
I'm also wondering how this works visually. I often find if things are just messy then I hate it and feel like I'm cluttered. But if something is kept clean and structured then I'm happy for it to stay as long as it gets out of my way when I don't need it.
I'm wondering if bookmarks are the same. If I don't need you disappear. But when I want to get it back then I want to find it in a clean and organised way.
The problem is I don't want to invest anytime in the process of managing the clutter. I want to manage itself.
Another commenter mentions going on a bookmarking spree when investigating a specific topic. Helping classify and process the results of those sprees seems like it would be helpful.
IMO a lot of other uses of traditional bookmarks range from pointless (I can instead easily type/auto-complete my favourite domains) to better served by specialist apps (news aggregator sites + caching read it later apps being a great example).
That's a very interesting use case and I can see how that would be valuable. I share a similar thought on bookmarks as in right now they are very permanent things when what I really want is like a temporary scrapboard that automatically disappears when I stop adding stuff to it. What do you think would that be useful ?
That's a very interesting perspective are you mainly using bookmarks for very important content? Do you ever just want somewhere to put stuff temporarily as you're browsing?
When I'm interested in something (e.g. cryptography) I open a bunch of tabs with usual suspects (google for cryptography, crypto stack exchange, google for crypto books...) and crawl these for even more tabs. Once I get a broad base of subjects to learn from, I slowly read these tabs and perhaps open more from these.
More often than not, I run out of time, so I have to temporarily store these tabs. I use my browser bookmarks for this.
My real bookmarks (real as in "the way bookmarks are intended to be used") are just in the bookmarks toolbar instead of hidden in bookmark folders.
I don't store important stuff in bookmarks. Bookmarks are not important. Important stuff is left as an open tabs to be reviewed ASAP.
That's interesting. It's very much what I assumed we use tabs to store the temporary stuff that we need right now or in the very short term. Bookmarks are not a solution engineered towards this very temporary way of working. However tabs are not the ideal solution either they are just a work around. I often find I want a convenient and temporary place to put this short lived content and it should disappear when I stop using it. What do you think ?
