996 karma · joined October 22, 2012
This was a really cool service, sad to see it go. It took 7 days to receive the fitting suit. We ordered 1 jeans, 1 t-shirt, 1 long-sleeve shirt and it took about 40 days to be shipped from ZOZO then about another week to arrive. They don't charge your credit card until the clothes are made and shipped.
Overall I was really happy with the service and the novelty of it made it a great gift.
It’s a totally different question to ask do I need a spa or a server rendered app, both can be dead simple or heinously complex or reasoned away to prove a point...
I 100% of the time want (1) to architect my UI as a collection of atomic, reusable components, (2) get page specific server rendered html per route, and (3) do JS in a sane way (manipulate DOM, manage client state, and support a series of interactions that do not reload the page.)
So, what are my options?
1. React/node 2. Sacrifice one of the above.
Award winning, real time tactical multi and single player game with a map maker and a mod system. So diffeeent from their other titles.
https://en.m.wikipedia.org/wiki/Myth_(series)
Fond memories of the “recon” WW2 mod that transformed the game of 1 on 1 managing an army of dwarves and warlocks to team vs team each individual controlling 1 army man.
(Edit) If you want to play it, the game is still supported (with a release in Nov 2018!) here http://projectmagma.net
Anyways, I found the article very informative because we weren’t sure what happened, it was such an anomaly we thought all our data was bad for the day, but it turned out to be an early Christmas present I guess.
Postmortems of things that affect a ton of businessses and people seem newsworthy to me. And while this isn’t a very detailed one, it’s more information than I could find anywhere else - we assumed it was a costly fat finger mistake.
It is worth it, there's still a lot of traffic, but it's a different model and elegant, interactive browser experiences aren't the target.
Minutes spent, repeat, and quality traffic continues to move toward native apps. GDPR and ad-blocking represent increasing risk + decreasing revenue with the status-quo media web experience.
So the status-quo is becoming prioritizing search engines, social scrapers, and a well-designed URL funnel that pushes traffic toward your native app where you can still monetize with display ads, reliably autoplay video with client-side video ads, and push notifications that result in actual traffic.
There are strategies for monetizing on the web (server-side ad stitching, integrated marketing, pay-gates, hell - just buy traffic to your site that you know doesn't have ad-blockers) but sometimes it's counterintuitive to funneling traffic to native.
Ultimately it requires investment in Product/Creative/UX/Dev to define and sell-through a vision/strategy for web to decision-makers when those decision-makers are seeing numbers that suggest even the investment to define the web strategy is a poor investment - let alone investment in developing and maintaining it.
There’s no browser api that tells you if autoplay is supported, and you won’t get meaningful errors when you try to autoplay when you can’t.
Ultimately the right solution is to just-don’t-autoplay-ever, but it’s a hard sell when you see a 20-40% drop in VOD begins when you remove autoplay.
I’m not sure how to even approach Chrome deciding to autoplay “sometimes”. You have to tell the video player to autoplay a video a.m3u8, but swap that out for preroll.m3u8 before you know if any of it is going to work at all. If it fails, you’re gonna see weird errors in IMA3, or at the video player level, none of which really help you decide how to gracefully handle the situation.
So yeah, if you have client-side preroll, just don’t autoplay I guess.
Thread: Electric scooters in SF are a good idea, poorly implemented. There are 4 scooter startups in SF & not one of them thought about the optics of what vacant scooters in everyone's way looks like or what it does for their name?! This is why design leaders won't shut up about empathy.