we hate how it looks on mobile. Should have prioritized it from launch...
-
-
Replying to @theWinnower @o_guest
I think there’s a benefit to releasing early and take it from there.
1 reply 0 retweets 1 like -
Replying to @gedankenstuecke @theWinnower
I mean in terms of css, release anything in any order. But I wrote a mobile-ready & -first website in a day.
1 reply 0 retweets 0 likes -
1 reply 0 retweets 1 like
-
Replying to @o_guest @theWinnower
I know, my blog where the article first appeared is responsive. But a larger publishing system is != jekyll. :D
1 reply 0 retweets 0 likes -
Replying to @gedankenstuecke @theWinnower
of course! But the css will still be a mobile ready/first framework, and that's what we're discussing.
1 reply 0 retweets 0 likes -
Replying to @o_guest @theWinnower
sure,just saying there might be constraints/reasons for initial decision, even if we all don’t like the outcome :D
1 reply 0 retweets 0 likes -
Replying to @gedankenstuecke @theWinnower
yep, my educated guess is usually it's time*skill constraints. That's what I learned in comp sci undergrad.
1 reply 0 retweets 0 likes -
Replying to @o_guest @theWinnower
yep, and financial resources, which limit the other two factors :)
1 reply 0 retweets 1 like -
Replying to @gedankenstuecke @o_guest
keep trying to hit like more than once on this! :)
1 reply 0 retweets 1 like
sad but true, altgh designers oftn gt shafted too & work for free. Money is always the prob 1 way or another.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
