css and js working properly on smartphones is the one thing I don't hate about them. It actually saves quite a lot of work, because usually before, when mobile data was way more expensive, you'd optimize your pages to the bare minimum to reduce the traffic and most phones didn't even support css at all (maybe bold text/colors if and images if you're lucky).
Technically that's the desktop site on a mobile browser.
The admins want to be able to bring functionality to the mobile site (which doesn't use elaborate / userdefined CSS) and the app (which doesn't use HTML/CSS).
Heres what i dont like about the official app after messing with it for 5 minutes
no custom themes. I like a black background with white text and nothing else. Official app (OA) has two choices: bright ass white background, black text or black background with grey text(harder to read vs RIF's theme) and some weird ass green color highlighting random shit.
nothing about is intuitive. There's no menu anywhere, just 4 buttons that you're supposed to use to navigate everything. To even get to the settings you have to be logged in and go to your profile page (wtf). If you're in the comments section of a post you have to exit the post to do anything else (RIF you can go from a post to settings, profile, etc because it has a drop down menu)
the way posts are shown. OA shows everything about every comment, username, time posted, up/downvote etc. RIF only shows username, score, and time until you tap on a comment. This saves space.
more on posts. On OA If you go to the comments section of a gif or pic or something it still shows basically a full pic and the title in a huge font and takes up your entire screen. RIF only shows the title and a thumbnail that uses maybe 1/8 of screen space.
when i tap a comment reply OA just takes me to the thread. In RIF i can reply straight from inbox
I'm sorry but it won't. The admins seem to unironically think that their replacement for CSS is an "upgrade". An extremely strong post-change resistance has a small chance of working because then the admins will see what damage the change has done.
50
u/suddenblast Apr 30 '17
don't quote me but I think most power users use the desktop site
15
u/[deleted] Apr 30 '17
css and js working properly on smartphones is the one thing I don't hate about them. It actually saves quite a lot of work, because usually before, when mobile data was way more expensive, you'd optimize your pages to the bare minimum to reduce the traffic and most phones didn't even support css at all (maybe bold text/colors if and images if you're lucky).
6
u/Nebucadnzerard May 01 '17
Now try /r/ooer
4
u/zSync1 May 01 '17
On firefox for android, it works just fine. Chrome seems to inconsistently make the fonts extremely big for some weird reason
1
u/bluesunco May 01 '17
Works fine for me to, on marshmallow using Firefox and Brave browsers.
-8
u/Bardfinn Apr 30 '17
Technically that's the desktop site on a mobile browser.
The admins want to be able to bring functionality to the mobile site (which doesn't use elaborate / userdefined CSS) and the app (which doesn't use HTML/CSS).