5 ms·
This looks really nice, kudos! Here are my few (hopefully constructive) comments: - The website looks great but quite heavy: 29 requests, 17.66 MB transferr
by boramalper 8y ago
This looks really nice, kudos! Here are my few (hopefully constructive) comments:
- The website looks great but quite heavy:
29 requests, 17.66 MB transferred, Finish: 40.09 s
Maybe see if you can re-encode `history-device.mp4` and `spaces-device.mp4` since they constitute the 78% of the traffic. =)
- I liked all the features you've introduced, but loved the way you've designed them!
- Kudos for getting the tagging right! Many developers expect users to tag their content, and tags were the next-big-thing at some point where there were tag-based file systems[0], photo and video galleries that expected you to tag each of your photos, and so on; but what really worked was automating the process of tagging! Everyone can agree that Google or Apple Photos are miles ahead of digiKam or Picasa when it comes to finding what you are looking for. I am glad that you didn't delegate that responsibility to the user.
- I think you should've put it on the AppStore first before sharing it; I would download it right away right now, as with many other people, but how many of us would remember Refresh a month later?
- I'd love to have branching history as well: so I have a tab and it has a linear history through which I can either go "forward" or "backward". Now, if I move backward in history, and click on a different link in that page, the history should branch at that point so that I won't loose the track of my previous "forward" pages when I click on a link in a previous page.
- Maybe not as satisfying, but I'd also consider developing add-ons for Chrome and Mozilla; some people would be reluctant to change their browser, but they'd be more comfortable adding exciting add-ons on a reliable browser.
All the best!
[0]: https://en.wikipedia.org/wiki/Tagsistant https://en.wikipedia.org/wiki/Tagsistant
- skrebbel 8y ago> I think you should've put it on the AppStore first before sharing it It's not a browser. It's a browser design. (plus a bunch of not-really-functional prototypes). I hope it becomes reality but so far this is basically the The William[0] of browsers. The William also never happened even though we all really wanted it to. [0] https://www.youtube.com/watch?v=2wBe3SDCcz8 https://www.youtube.com/watch?v=2wBe3SDCcz8
- TeMPOraL 8y agoHoly hell! Never seen that before, and I very much want it now. Do you know why it didn't happen?
- 3stadt 8y agoIt was never meant to become a real product. The concept was made by Greg Beck, a dude from Ohio, as some sort of a "hey, wouldn't it be nice if..." thing. Or maybe as part of his showreel as a product designer. Sadly, his website[0] is down, but you can find a version without images in the archive[1]. The domain name is still registered though. You could write him an email and ask what happened. ;) [0] http://becktothefuture.com/ http://becktothefuture.com/ [1] https://web.archive.org/web/20111208083212/http://www.becktothefuture.com/projects/The-William.html https://web.archive.org/web/20111208083212/http://www.beckto...
- TeMPOraL 8y agoThanks! I sent him an e-mail!
- zanedb 8y agoPlease do share his response, I'm curious (via response to this comment, or my contact info in my profile).
- saidinesh5 8y agoIirc Electrolux was working on a fairly similar concept back in 2012-2013. Can't find the exact link for the touch screen one but these demos should be fairly similar: https://m.youtube.com/watch?v=dK1IVk_NiGY# https://m.youtube.com/watch?v=dK1IVk_NiGY# https://m.youtube.com/watch?v=qboMSdgxZ4s# https://m.youtube.com/watch?v=qboMSdgxZ4s# https://m.youtube.com/watch?v=QSJzq8rbR2c https://m.youtube.com/watch?v=QSJzq8rbR2c
- Jasper_ 8y agoMaybe because creating a touch-sensitive surface that can heat up to cooking temperatures without melting the electronics next to it is harder than it seems? Just because something is in an After Effects mockup doesn't mean it's practical to engineer.
- jraph 8y ago> I'd love to have branching history as well: so I have a tab and it has a linear history through which I can either go "forward" or "backward". Now, if I move backward in history, and click on a different link in that page, the history should branch at that point so that I won't loose the track of my previous "forward" pages when I click on a link in a previous page. Implemented in Netsurf, with a nice history tree with screenshots :-) I'd really like to see this in mainstream browsers.
- seandougall 8y agoWould be a real nice concept for the undo stack as well, UI challenges aside.
- niutech 8y agoThere is an extension for Chrome called Visual History: https://joelgustafson.com/projects/visual-history/ https://joelgustafson.com/projects/visual-history/ or Histree: https://chrome.google.com/webstore/detail/histree/lngppkkhjifheiegfeloipgaeomjfgbf https://chrome.google.com/webstore/detail/histree/lngppkkhji... or Tree History: https://chrome.google.com/webstore/detail/tree-history/kfgnedbkboedeildkjiodjhpldgfekjm https://chrome.google.com/webstore/detail/tree-history/kfgne... or Brancher: https://brancher.io/ https://brancher.io/