Review of Maxthon Nitro final []

Recommended Posts

Maxthon Nitro is going to fail. The final version of Nitro is so lacking in the most essential features that it's laughable to even call it a final version. Nobody wants a browser stripped down to Notepad's level. It's unproductive and doesn't have features that save time and effort.

Would you prefer to write an essay using MS Notepad or MS Word? Would you prefer to edit a photo using MS Paint or Adobe Photoshop? Same concept.

Would you prefer to use Nitro which loads fast but is so lacking in features that it actually wastes your time during usage? Or would you prefer a powerful browser that take longer to load but saves you lots of time during usage with convenient features?

Maxthon should return to its roots as a feature-rich powerful web browser, like back in the glory days of version 1 and 2. Similar to the design philosophy of the Slim browsers:

As it stands now, Nitro makes it look like Maxthon is trying to cut costs, laid off most of its developers, and no longer have the budget to stay competitive. Meanwhile, the target casual audience of Nitro will not bother to shop around for a new browser, and they will just stick with Internet Explorer for simplicity.

The fundamental thinking behind Nitro is flawed, and Maxthon needs to recognize this and turn around quickly.

Verdict: 1 out of 5 stars.

Link to post
Share on other sites

i wish maxthon would not waste any time with nitro, and simply focus on the main maxthon browser and add more powerful productivity features to it, as well as addressing its bugs. the progress of maxthon 4 has been very slow and disappointing. maxthon 4 is still missing a lot of useful features that were in maxthon 2. and now there's nitro, which further proves that maxthon's direction has been going backwards.

Link to post
Share on other sites

hi, I like very much this new browser, but I'd like if in the future you'll add some features that maxthon user I think adore:

- add multilanguage support... I understand English well but I prefer to have a browser in my native language (Italian)

- add maxthon passport to save and have all my accouns credentials on all my devices

- add the bottom that re-opens closed windows with left click of the mouse and opens menu of recent opened windows.

I hope to find these features in the feature, because these are the reasons I use Maxthon from a long time.

Link to post
Share on other sites

But the purpose of Maxthon Nitro is to have less features and super speed. :) If you add more features then speed will be slower and we'll have 2 different Maxthons. :titter:  One Webkit and one Chromium. emotion-5.gif

Edited by Xahi4475
Link to post
Share on other sites

The answer to MXnitro problems is quite simple and it was the original idea from Opera. What is it? Well you offer a barebones browser but you also offer your own extensions to add power to the browser how you like. Opera didn't do any of their own extensions at the time only third parties. That is how I would do with Nitro. Personally I'd further tart up Maxthon 4 and correct the lagging issues on some sites and with multiple tabs. I'd also look at doing a 64-bit Maxthon 4/5. If Maxthon could sort those few issues add a couple of extra features then it would be very good. For the time being I've gone back to Opera 27 Beta until the bug's fixed in 28 Developer.

Link to post
Share on other sites
  • 5 weeks later...

there is more proof that the new trend in browsers is to go feature-rich. such as flashpeak slim browsers, spartan browser, vivaldi browser, etc. maxthon should return to focus on being a power user browser, not waste time with nitro and get left behind.

Link to post
Share on other sites

Nitro is not supposed to be feature rich.

It is supposed to be lean and mean. It's like a stripped down car. You remove all the creature comforts that add weight to the car so that you are left with the bare bones and a very light car. The result is a car that's fun to drive, because it goes like stink and handles well, but it has no radio, no carpets, no electric windows, no sound insulation, and so on. If you are the sort of person that would trade a bit of speed for some additional features, then that car is not for you.

I used to drive a Caterham as my everyday car. It's not for everyone, but it was wicked fast, it handled like a go-kart, it was very noisy, it had no creature comforts whatsoever (apart from seats), and every time you got inside you hoped it would not rain. Not for everyone, but it was a blast!

From my own testing, by using Nitro every day as my default browser for over a week now, I think it really is fast. And yes, I do go back to other browsers (Chrome, Firefox) to compare, so it's not just psychological. By the way, the HTML5 test (which some people have mentioned) is not about speed, it's about coverage of HTML5 features. Maybe there is some speed hammering benchmark test says it doesn't have the highest score (is there?), but overall speed is more than just hammering one aspect. The biggest impact for me is the perceived loading time for a new page, which is really fast.

Personally I also like the simplicity of it. Less is more. Long ago, I used to use Outlook for email, and then I moved to Gmail. Hands down Outlook has tons more functionality, but Gmail is refreshingly simple and I can do everything I need with very little mental effort (and it gives me access from all internet devices, but that's not my comparison here). There's no going back to Outlook for me.

So Nitro is supposed to be lean and mean, and refreshingly simple. That's that whole idea. If it's not for you, then that's fine and you have other choices. It is for me.

I think there are some pieces are functionality that could be added without compromising the vision of Nitro. UI commands can be added to context menus for example. This should not interfere with speed or visual simplicity.

I love the mouse gestures by the way, which is something I used all the time with Chrome (Smooth Gestures extension), and it's nice to see that the same gestures do the same thing. Mouse gestures are just a way to execute a UI command, so these should not affect performance. Someone commented that they might be taken away at some point. I hope not. By the way, where are they all documented?

Ad blocking (something that people keep mentioning) is an algorithm that runs while the page is being loaded and rendered, and this could well slow things down, even though the resulting rendered page is simplified. There is an argument that ad blocking reduces the amount of data that needs to be downloaded, which should improve speed, but it also introduces processing delays into an algorithm that would otherwise just request everything in parallel. I imagine another objection to providing ad blocking is that this would call for a add-in framework, and then if you open this up you've opened the door for slowing things down and you are back where you started with a bloated slow browser.

My enhancement list would be:

History. According to the tool tip, right-clicking on the Back button should show navigation history, but it does nothing.

Keyboard shortcuts. Even the standard ones are missing: prev/next tab, close tab, back/forward, etc.

Context menu commands for 'close other tabs' and 'close tabs to the right'.

Support for multiple windows and for dragging tabs off into a new window, or between windows.


  • Like 1
Link to post
Share on other sites