Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Announcements Slashdot.org

Experience the New Slashdot Mobile Site 384

Posted by Unknown Lamer
from the tastier-than-bacon dept.
After many months of effort, today we've brought the new mobile site out of beta. Featuring an interface optimized for touch devices, we think it's a huge improvement over the old mobile interface. You'll find comments easier to navigate, the most popular stories highlighted at the top of the page, and a surprisingly pleasant interface for navigating old polls. We've also spiffed up user profiles, resurrecting and improving the friend/foe system in the process. And that's not all: we're pleased to announce that you can login to Slashdot in general using various social media accounts, so if you use Facebook or Google+ there's no excuse not to enjoy the benefits of being a registered user, without the hassle of creating yet another account. Our weblog has a few more details. As always, if you encounter any issues let us know by mailing feedback@slashdot.org.
This discussion has been archived. No new comments can be posted.

Experience the New Slashdot Mobile Site

Comments Filter:
  • No thanks (Score:5, Insightful)

    by Desler (1608317) on Wednesday February 06, 2013 @11:30AM (#42809453)

    No thanks. It's pretty terrible. Can you also stop the chooser popup please? I want to use the classic site without constantly bombardment with a popup.

    • Re:No thanks (Score:5, Insightful)

      by motang (1266566) on Wednesday February 06, 2013 @11:34AM (#42809501)
      I second that, the classic is great!
      • Re:No thanks (Score:5, Informative)

        by jest3r (458429) on Wednesday February 06, 2013 @12:06PM (#42809951)

        I third that. I don't understand why we need a dumbed down version of the site when my phone can display the full site just fine? I'v enever had a problem browsing the full site and prefer it.

        • Re:No thanks (Score:5, Interesting)

          by pmontra (738736) on Wednesday February 06, 2013 @12:12PM (#42810049) Homepage
          I fourth that. And fix the theme so it works with Firefox (mobile). It's a blank page right now. Not that I use FF on my phone often, I'm using Dolphin most of the time but I wouldn't mind if more site were compatible with more browsers.
          By the way: polls don't work in the mobile theme in Dolphin: the options don't display. I think I'll keep using Classic.
          • Re: (Score:3, Interesting)

            by Tempest_2084 (605915)
            Can I fifth this or is it redundant by now? The mobile site doesn't offer anything worth switching for and I'm getting tired of that damn popup.
            • Re:No thanks (Score:5, Insightful)

              by jackb_guppy (204733) on Wednesday February 06, 2013 @12:41PM (#42810501)

              And I thought it was just me.

              Issues:
              1) does not scroll smoothly or nicely
              2) scrool is thought of 1/2 time as a cick - so off to storie no down to next page.
              3) I do not what tracking by facebook or others on Slashdot site
              4) pop overs are annoing specially when the X is to small to touch or acts like click. Touch interfaces need to big enough for touch! Fat fingers are fat fingers!

              • Agreed 100% !!

                The mis-scrolling and mis-clicking is the most frustrating aspect of the UI.

                The _one_ thing I DO like is the lack of margins. There is no sidebar forcing all the comments to be indented wasting whitespace.

              • by nschubach (922175)

                The popup that comes up to ask you to switch to the mobile site seems to have a fixed position hit boundary. If you scroll the page a bit, the buttons no longer work for me on Android ICS.

              • by Evtim (1022085)

                Sorry to report that it does not even show on my phone - I get white screen. HTC Desire. Could be that my Android version is too old (2.2) or something. Not my fault - I don't get OS updates from HTC. I hope it gets fixed.

          • Re:No thanks (Score:5, Informative)

            by nmb3000 (741169) <nmb3000@that-google-mail-site.com> on Wednesday February 06, 2013 @01:12PM (#42810903) Homepage Journal

            It's also a blank page if you use AdBlock+ with EasyList. The rule ||googletagservices.com^$third-party breaks their requirement for Google Tag Services, and they weren't bright enough to handle this failure gracefully. Same with NoScript -- unless you've allowed googletagservices.com (and I've managed to browse the web fine for over a decade without it) then it's blank-screen for you.

            Pretty sad.

    • Re:No thanks (Score:5, Insightful)

      by SydShamino (547793) on Wednesday February 06, 2013 @11:34AM (#42809517)

      The constant popup is annoying. I would use the mobile site, though, except when I said "yes" to the popup a few weeks back, then tried to reply to a comment, Safari crashed on my phone.

      Can you let us set a user preference in our account as to whether we want the mobile site or not on mobile devices? Bonus points for letting us set it on a per-browser-string basis, so I could use the mobile site on my phone (assuming it doesn't continue to crash) but the full site on my tablet.

    • Re:No thanks (Score:5, Insightful)

      by Anonymous Coward on Wednesday February 06, 2013 @11:51AM (#42809737)

      Roll Back!!! Roll Back!!! Roll Back!!!

      abort, abort, abort!!!

      News flash, techie people prefer functionality to glitz. I prefer the desktop site on my phone. New mobile version isn't appealing.

    • by EkriirkE (1075937)
      Ugh. Seriously. I can only see headlines at first on the mobile version. I can't even bother to expand all the stories to get the synopses.
    • by Fallon (33975)
      I get to Slashdot via my RSS feed, which goes directly to the article. The pop-up then boots me back to the root website rather than staying on the article I was trying to view if I tell it to use mobile. On Android, if you scroll down at all, you can no longer click on the mobile or classic buttons too, extremely annoying. You have to scroll up to the top of the page to be able to click on the buttons & make it go away, despite the pop-up scrolling down the page to cover stuff up.
    • Re:No thanks (Score:5, Informative)

      by jennyscript (2714045) Works for Slashdot on Wednesday February 06, 2013 @12:29PM (#42810315)
      Hi, I'm a mobile dev responsible for the new app. The mobile site chooser popup is designed to go away and not reappear when you choose "Classic" but obviously you guys are not seeing that behavior. We'll get a fix out soon so the site will really remember you don't want to use the mobile app. Sorry about the extra popup in the meantime.
    • by Jim Hall (2985) on Wednesday February 06, 2013 @02:18PM (#42811909) Homepage

      I'm confused why anyone - especially a technology-driven site like Slashdot - would create a "separate but equal" website just for mobile devices. It doesn't make sense these days. What's better is to build a responsive web design [wikipedia.org] that scales down appropriately to the device. Then we don't have to visit a separate website with different branding to get to the same content on a mobile device.

      In a responsive web design, you might still choose to detect a mobile browser, and then set the comment browsing level to "5" or maybe "4". That's arguably the only thing you'd need to do that requires knowing the type of the client device.

  • And I don't like it. Please stop with the popup every single time I open the browser on a mobile device. I'm a creature of habit as I'm sure many others are here and the old mobile interface isn't so far a divergence from the desktop site that i'm not sure where things are. The problem with the new mobile site is it's too different. This is not a social networking site. Please don't try to make it into one.
    • Re:Tried it (Score:5, Insightful)

      by Cinder6 (894572) on Wednesday February 06, 2013 @12:14PM (#42810075)

      I'm using it right now (though posting from my desktop). Honestly, it's a lot faster than the old site, and navigation is more friendly to touch devices. Most importantly, comments load better than before. With that said, two things bother me about it:

      1. The aesthetic is completely different from the desktop site, to the point that I wouldn't know it's Slashdot if it didn't say so at the top. This isn't a huge deal, but brand recognition is important.
      2. The article summaries are shortened on the front page, and you have to tap the headline in order to load the whole thing along with contents. This breaks up the site's flow and makes it harder just to peruse articles. Take, for instance, the following excerpt:

      Two economists at the St. Louis Federal Reserve have published a paper arguing that the American patent system...

      The shortened summary offers nothing of value to me; the headline is actually much more informative. What I think needs to happen is either enable full, unshortened summaries, or write a summary of the summary for mobile devices. One of those options is silly, the other is reasonable.

      • by jest3r (458429)

        YES

        If the mobile site still LOOKED like Slashdot I think people would be more open to it.

        But it looks like any Generic news site ...

        I remember when they redesigned Slashdot 5 years ago ... and the new design retained the "feel" of the old design. The mobile site does not retain the Slashdot feel. Even hardcore old school Emacs guys have a certain affinity towards the way things look and feel here. So don't mess with that.

      • Yes. I don't like the article "snippeting" on the main page either. It's the main reason why I didn't explore the beta very much; reading the articles so I know which ones I want to load the comments on is a core function.

        If all I wanted was RSS snippets, I'd read Google News instead.

  • by DogDude (805747) on Wednesday February 06, 2013 @11:33AM (#42809489) Homepage
    Doesn't do anything on my phone. The "loading" bar just sits there loading, and no articles ever come up. Perhaps this was announced a bit prematurely...?
    • It requires JavaScript to work.
      • by TheSpoom (715771)

        In that case, it should have a noscript element telling you to turn on Javascript, at the least.

    • by AmiMoJo (196126) *

      It loads on my Galaxy S III but as soon as you try to drag and scroll it opens the article under your finger. I submitted a bug report months ago and figured it would be fixed before launch, but apparently not.

      It works okay if I switch to Chrome.

  • Sorry, not so good (Score:5, Insightful)

    by C R Johnson (141) on Wednesday February 06, 2013 @11:33AM (#42809491) Homepage

    Every time I have tried the new mobile site my experience was not good.
    I can't even scroll down easily and when I do it jumps into an article that I didn't select.
    And it doesn't look good.
    Maybe it's opera mobile's fault. Maybe you need to think on this some more.

  • Doesn't that imply that there was a mobile site before? To the best of my understanding there was never a mobile slashdot site before now - or at least, not one that worked. I also like how the "new" mobile site launches now thta BlackBerry is considered to be a marginalized niche player - I had pointed out before that slashdot would crash most Blackberries and they always made excuses for not doing anything about it. Now that BlackBerry is no longer viewed as particularly relevant they can more easily
    • by Psyborgue (699890)
      There was a mobile site. It only differed slightly from the desktop site so it wasn't too much of a shock.
  • It looks ok and viewing comments is generally better but it feels a bit busy. The old mobile site with improved comment views would be best.
    • Forgot to add it's mostly just nesting that's an issue on the old one.
    • by Desler (1608317)

      But that would require actually expending effort to fix things. That's never been the Slashdot way. They couldn't even fix the pagination bugs in the version before they did the whole discussion overhaul. They want to chunk out new code, not do "boring" software maintenance.

      • I assume a third a third party was hired to do it and that's why they opted not to follow the theme at all and go with something completely different and didn't care enough to make it work on desktop browsers even if really it doesn't have to.
  • I've had zero problems using the desktop version on my mobile devices, especially my tablet. Now I get a popup to deal with everytime. Seriously, the regular site is fine. I appreciate the effort but it's not necessary. Honestly I'd rather you guys spent time fixing bugs in the RSS feeds that perhaps someone reported months ago and go ignored.

  • What about ipv6? (Score:2, Interesting)

    by DeAxes (522822)
    Forget mobile, I'm still waiting for Slashdot to have a AAAA record.
  • by Anonymous Coward on Wednesday February 06, 2013 @11:39AM (#42809583)

    I hate it and it's terrible and it sucks and I hate it and it's different and why did it change and it's terrible and it's different and it's not working on my obscure phone so it's useless to everyone and it sucks and nobody should ever ever ever ever ever use it ever again and I don't like it. It's stupid. I'm a nerd, so I know this sort of thing. I'll click the link later when I've got time to look at it.

  • Do Not Want (Score:5, Insightful)

    by SuricouRaven (1897204) on Wednesday February 06, 2013 @11:39AM (#42809587)

    "we're pleased to announce that you can login to Slashdot in general using various social media accounts,"

    Why would I want to do this? On Slashdot, of all the sites on the internet, people value their privacy. Perhaps we don't want the data-miners at Facebook to monitor our slashdot usernames, cross-correlate post times against estimated work hours and calculate our estimated slacking-off coefficient to better target advertisments? I'm entirely happy to have lots of seperate accounts - it beats 'One Account to Rule them All.'

  • by Internal Modem (1281796) on Wednesday February 06, 2013 @11:40AM (#42809593)
    You guys did something wrong. In mobile Safari when I try to scroll down the page, it often detects my touch as a click and opens a story I don't want to read. This isn't a problem with the browser because it doesn't happen on any other mobile site. It seems to be a problem with the size of your click-able regions. I'm not sure what kind of beta testing was done, but it obviously wasn't enough.
    • by chihowa (366380)

      I specifically reported this during the alpha and the beta and nothing at all changed. In fact, from a user perspective, nothing at all has changed from the alpha to the launched site, so I don't think they gave a shit about bug submissions. Since alpha, the short summaries, fucked up scrolling, weird swiping behavior, etc have all been reported by many users.

  • Worthless! (Score:3, Informative)

    by Anonymous Coward on Wednesday February 06, 2013 @11:40AM (#42809601)

    You IGNORED every constructive comment that people made regarding this mobile interface. You INSISTED on doing it the stupid way.

    Nobody is going to use your mobile interface when it makes browsing slashdot MORE WORK than before. We can't even get full article summaries on the front page! What kind of bullshit is that?

    And I think it's just wonderful how every mobile user gets a banner suggesting they switch to the much more heavily ad-strewn mobile interface. Congratulations slashdot, you've managed to create a mobile interface that is WORSE than the full site on just about every level. way to ignore your customers.

  • by Imagix (695350)
    Hmm... not impressed. Browse to the top site, the browser goes unresponsive for about 8 seconds. Browse into a story, reasonably fast. Browse back to the stories list, another 8 second lag. Can't even scroll. (Chrome on an iPad 3, Wifi)
  • by knarf (34928) on Wednesday February 06, 2013 @11:42AM (#42809615) Homepage
    1. it is faster
    2. I can open a bunch of topics in new background tabs for later perusal
    3. did I mention it was faster?
    4. it works without JavaScript

    It has one disadvantage: I have to click away a popup which asks me to use the new site, time and again...

  • scrolling lag (Score:2, Informative)

    by Anonymous Coward

    The mobile site lags badly while scrolling on an Android device using chrome. Any chance of fixing this?

  • Needs work (Score:5, Informative)

    by jimpop (27817) * on Wednesday February 06, 2013 @11:45AM (#42809659) Homepage Journal

    When following a link to /., if I answer Yes to the pop-up prompt, i get redirected to http://m.slashdot.org/ [slashdot.org] and NOT the story I was linking to

  • *makes a-ok sign, then glares* It stinks.

  • Hey dummies, you broke scrolling during the beta. It simply doesn't scroll properly on the default Android browser. Something is mucked up with touch event handling. Please fix this. That is why everybody keeps saying they prefer classic mode - at least you can scroll properly.

  • A little better (Score:4, Interesting)

    by bsharitt (580506) <brandon&sharitt,com> on Wednesday February 06, 2013 @11:48AM (#42809713) Homepage Journal

    The old mobile site wasn't really mobile, so I guess anything is better, though it's a pretty slow and heavy site it seems. It looks to be working in Firefox for Android now, that's an improvement over the last time I used the beta.

    So how long until /. wraps up the new mobile site in an app wrapper and advertises a "mobile app" for iPhone and Android like seemingly every other website out there?

  • Classic (Score:4, Insightful)

    by Bogtha (906264) on Wednesday February 06, 2013 @11:51AM (#42809735)

    WeÃ(TM)ve built the mobile user experience with the future in mind

    And yet Slashdot is still incapable of handling nonASCII characters. Unicode is over 20 years old, guys.

    Is there any reason why this was done as a separate site and not with a responsive design? Separate mobile sites are the old-fashioned way of doing things.

    • Re:Classic (Score:4, Insightful)

      by Desler (1608317) on Wednesday February 06, 2013 @11:58AM (#42809849)

      Yes but Unicode and IPv6 are clearly just fads. They aren't nearly as important as Facebook/Google+ login and filling out the buzzword bingo card with all the fad frameworks:

      We built this app using the latest technologies and frameworks such as Backbone, Zepto, Underscore, Hamstache, Jasmine, and Sass.

  • by thrill12 (711899) on Wednesday February 06, 2013 @11:52AM (#42809751) Journal
    Finally, get ready for... [rant mode on]
    I am sick of having the message "would you like to try beta or classic" every time when I browse Slashdot on my Chrome browser under my Nexus. I want the *regular* site, or something as close to it as possible. I even cannot click on the "classic" button... First lesson for new designs: if someone says *not for me* then leave them alone or they will leave your site alone.
    Why should I have to press "request desktop site" each time I simply want to read an article ? This is not a PALM III where I zoom in with the Plus and Minus keys: my browser is more powerful than a Windows IE6 browser (feature wise), faster than many regular old Pentium IV's and pinching is good enough to get around the site.

    [rant mode off]
  • by zenyu (248067) on Wednesday February 06, 2013 @11:52AM (#42809759)

    When I click on something it takes forever for the UI to respond. There is no visual feedback so until I realized that the new UI was just 200x slower than the old one I clicked on the things 5-10 times thinking the clicks just didn't take the first n-1 times.

    I've obviously switched back to using the desktop site on my mobiles, but there is a popup on every page load asking me to try the mobile site! Sheesh!

    You need to fire the contractors involved and hire some people who know what they are doing.

  • So so (Score:3, Insightful)

    by Anonymous Coward on Wednesday February 06, 2013 @11:53AM (#42809767)

    I jused the (new) mobile site for the first time on an iPhone 4S and had no issues whatsoever. Although I like the overall look and feel of the site I don't think a redesign was all that necessary. Sorry, devs :) But don't listen to the haters, they wouldn't like it no matter how it had turned out!

  • On my Note 2 the mobile site is having trouble registering any scrolling. It's most likely due to bad javascript.
  • by EmagGeek (574360) <gterich@@@aol...com> on Wednesday February 06, 2013 @11:58AM (#42809841) Journal

    What the fuck were you guys thinking?

    An, in general, what the fuck is going on with people designing user interfaces these days? It seems everywhere you go there's yet another abortion of a user interface.

    Seriously...

  • And it's making it difficult to navigate the site. Plus, there doesn't appear to be a way to get back into classic once you're in mobile. Looks ok, just needs functional work
  • While the virtues of mobile web is alluring to content providers, I prefer dedicated mobile apps over opening a mobile web page.
    Might I suggest Slashdot start out making a simple Apple and Android application. Until such time I will continue to use my Reddit mobile application when getting my news that matters.
  • I browse /. on my Nexus 4 and iPad, both of which display the full /. site perfectly. The layout of the site downscales rather nicely, and I've never had an issues with it. The "mobile" site, on the otherhand, is not my cup of tea. It just doesn't feel very slashdotty.
  • by pherthyl (445706) on Wednesday February 06, 2013 @12:09PM (#42810001)

    The new site is terrible. I really tried to use it for a couple weeks but had to go back (iPhone 4).

    The new site is significantly slower first of all, which essentially kills it right off the bat. Speed should be your #1 feature. If you can't make it faster on mobile, don't bother with the redesign just tweak the existing layout.

    It's also very glitchy as others have pointed out.
      - Scrolling down often results in a click.
      - After the page loads it jumps to the top again if you scroll down too fast
      - transitions are glitchy and slow. Don't use them they don't add anything.

    As for the announcement it is just full of fail.

    >> We've built this new mobile interface optimized exclusively for your touch smartphones and tablets.

    Why? The revolutionary part of the iPhone was that it could handle regular desktop sites and we could do away with WAP. Now we suddenly need a special site again? Just make sure that the layout scales well and you're done for mobile on a site that is purely about content. It's a different story if you're something like an online retailer where people want quick access to a few key functions (search, store locator, inventory, my account, etc).

    >> Read comments and stories in a mobile-friendly view (no more squinting!)

    Never had to squint on the old site. what's the problem?

    >> Most popular stories shown right at the top

    If I passed by a story earlier in the day what makes you think I want to see it again?

    >> See beautiful achievement badges

    I have no words. This is so stupid.

    >> Show off your latest Gravatar

    Yep, that's why I'm here.

    >> We built this app using the latest technologies and frameworks such as Backbone, Zepto, Underscore, Hamstache, Jasmine, and Sass.

    So you jumped on the bandwagon of stupidly named frameworks and used all of them because that's the thing to do these days. Surprise surprise, the end result is too heavy.

    >> Since there are so many mobile devices and capabilities, we targeted webkit browsers, and Android versions above 2.3.

    Sounds like browser support got worse then. Say it like it is.

    >> We didn't start sketching the blueprints based on what we thought a mobile experience should be - we asked YOU.

    Ah, that's the problem then. Design by committee and it shows.

  • by Pseudonym Authority (1591027) on Wednesday February 06, 2013 @12:10PM (#42810009)
    No thanks. It takes forever to load, it looks like shit, and its generally terrible.

    Now take that stupid popup thing that tells me to go to the mobile site. If I want to see your shitty social-web2.1-scalable-turnkey-webdesigner-solution I'll go to the god damn site myself. Whoever wrote this should be ashamed.
  • by jvj24601 (178471) on Wednesday February 06, 2013 @12:10PM (#42810011)
    I still use the Classic Discussion System (D1) and have my Threshold set to 2 (sometimes I reset to 3 or 4 as well). How can I have the mobile site honor that preference?
  • Too funny (Score:4, Interesting)

    by Jmc23 (2353706) on Wednesday February 06, 2013 @12:20PM (#42810163) Journal
    It sucks and apparently everybody but the designers think so. I wonder if the downfall of slashdot was when they started trying to run it like a business. Managers and designers that know nothing about their audience or apparently don't care. Though it makes sense to build an audience of idiots because idiots buy things. Nerds and geeks will roll their own.

    I really wish slashdot had an api to access posts so we could calculate the exact turning point. Definitely 2013 is when the tide has shifted.

  • by Andrio (2580551) on Wednesday February 06, 2013 @12:45PM (#42810545)
    I ran it through this software I have at work called "Mobile Internet Testing Environment" and it got a "MITE score" of 68/100. It's based on best practices for performance of a mobile site. The slashdot mobile site got penalized for things such as not having the JS at the bottom, for having iframes, not combining css/js, one http request error, no alt tags for images, and others.
  • by roc97007 (608802) on Wednesday February 06, 2013 @01:05PM (#42810829) Journal

    Overwhelming negative response. It makes one wonder what the design criteria were, or the Q/A strategy.

  • by jennyscript (2714045) Works for Slashdot on Wednesday February 06, 2013 @05:03PM (#42814153)

    Hi, I see a lot of you are having trouble with scrolls in the app being detected as clicks on stories. The team here has been trying to reproduce this, but failing. Here's a list of device / browser combinations I've tested:

    • iPhone 4s Safari
    • iPad 1 Safari
    • Nexus7 Chrome
    • Nexus7 Firefox
    • Nexus7 Opera

    The concern here is that there's some kind of common scrolling motion we aren't doing that's causing them to get interpreted as clicks. Are you holding your finger down longer? Pausing somewhere in the scroll? Is there horizontal motion in there? Is your scroll more of a flick? We've tried all those things and haven't seen it, so if some of you experiencing the problem would be kind enough to record a video of yourself making it happen (preferably on one of the above devices so we can reproduce it too), that would be great. There is no Slashdot Mobile QA team and our dev team is tiny.

Science and religion are in full accord but science and faith are in complete discord.

Working...