10 UXPin Product Updates You Might Have Missed

And now they’re here! From user requests to new features, big and small, we’ve shared some of UXPin’s updates from the last twelve months in one concise form.

 

1. Shadows

You can easily add shadows to the elements and customize their color, opacity, and relative position. It’s possible to combine multiple shadows together or create only inner ones. This heavily requested feature is available to all users.

2. Pen Tool

Use Pen Tool to draw shapes and icons directly in UXPin. Any drawn element can be viewed in spec mode and downloaded as an SVG. Creating custom icons and adding them to your design library has never been easier!

3. Tokens for Design Systems

Imagine this: your developers can have access to rich information with just one URL, opening possibilities for ultimate design consistency.

Now you can easily export your color and typography styles, as well as their full documentation, to JSON. For quicker exporting, you can use other popular formats including YAML, CSS, SCSS, LESS, and STYLUS, but without documentation.

4. Copy-pasting styles and interactions

Say no to tediously re-making interactions. You can now copy-paste them to elements with just a few clicks! You can also quickly apply entire styles (including color and typography) from one element to another, saving you so much time.

5. New pricing

We are excited to share that we now offer four different plans (starting from $9/month) with a variety of features tailored to your needs. Whether you’re working on a small project or with a complex design systems, we’re confident you’ll find the right fit among our new plans.

6. Resizing panels and UI redesign

Our UI has seen numerous iterations, but after our latest redesign we’re really proud of it. Not only is it slicker and more intuitive, but also it freed up a lot of screen space. We’ve also given you the freedom of customization — it’s possible to resize panels and toggle UI theme from light to dark. Great for contrasting your prototypes!

7. Performance updates

2017 was a year of constant performance improvements. Team dove into javascript and made dozens of micro-optimisations. Overall, we’ve decreased loading times by 30%, preview has become significantly stable, and complex design systems are scrolling smoothly. 2018 is no different and further upgrades are planned and scheduled.

8. In-app changelog

It was easy to lose track of our constant updates. Not a week passed without a deploy that addressed requests we heard or fulfilled our roadmap. With our in-app changelog, you will be notified every time an important feature or update is released.

9. Pasting from clipboard

The ability to paste an image directly from your clipboard into UXPin allows you to save precious time and makes prototyping even faster. Copy the image, paste it to UXPin, add interactions, send it to a client — a mockup is born!

10. Math operations

You can use basic math operations to determine the size or position of your elements. It’s also excellent when calculating proportions on the fly.

One more thing…

Last but not least, we’ve just launched our brand new desktop application. It has all the tools from the original browser version, in addition to some added improvements. Because it’s right on your desktop it’s always at hand — just one click away from your Dock or Taskbar. Having dedicated processes makes it faster and more reliable as well as uninterrupted from plugins and browser distractions.

You can get the latest versions here: MacOSWindows.

 

Join the world's best designers who use UXPin.

Sign up for a free trial.

M-Dot Sites Are Dying Long Live Responsive Design | UXPin

It’s official: the internet lives on mobile.

With mobile browsers overtaking desktop, a mobile-friendly site is no longer just a “nice to have”. This requires a shift in the web design process that M-dot sites just can’t sustain in the long term.

Illustration of responsive web design.

Source: “Boston Globe responsive website, featuring Apple Newton.” Antoine Lefeuvre. Creative Commons.

In this article we’ll explain why M-dot sites aren’t future-proof, and why responsive design is the responsible way to build mobile-friendly websites.

The Vulnerability of M-Dot Sites

Back when mobile browsing was new, M-dot sites made a lot of sense. Their faults could have been chalked up to inexperience — designers were scrambling to keep up with users before the mass proliferation of mobile devices.

Now, some years later, mobile devices became more complex, thanks to tablets and varying screen sizes.

So what exactly is mobile? Smartphone, tablet… watch, glasses? Even limiting it only to smartphones, what size screen? The diversity of mobile devices has grown exponentially since M-dot sites were first used.

This isn’t just our speculation, either. Pure Oxygen Labs reports that last year M-dot sites fell 20%, from 79% in 2013 to 59% in 2014, while responsive and adaptive (dynamic serving) sites rose 37% collectively. Of course, some stalwarts remain (like Facebook and Zappos, who maintain a M-dot site mostly for site load advantages), but it’s fairly safe to say that M-dot sites are generally dying out.

Screenshot of the Zappos website.

Photo Credit: Zappos

Let’s explore some of the reasons to abandon M-dot sites:

  • Users visit the full site anyway — Research from Web Performance Today shows that about a third (35%) of users choose to go to the full site if given the option.
  • Users spend more time on the full site — The same research states users spend 5.5 times longer on full sites than M-dots.
  • Full sites yield more revenue — The study also calculated that 79% of revenue from mobile sales came from users on the full site.
  • SEO/Google trouble — According to Google’s own guidelines, responsive sites will likely rank better. Not using an M-dot is a automatic boost in SEO.
  • Redirect time — While M-dot sites load faster in theory, the extra time of redirecting from your full site to the M-dot (unless the user types the M-dot’s URL) is unnecessary. Alongside the other drawbacks, is it worth it?
  • Social sharing problems — M-dot links opened on a desktop are, at best, ugly. Given how this is not even an issue with responsive design, the path to better social settings is clear.
  • Expensive maintenance — When you add an extra codebase, you also add more maintenance cost in the long-run. You’ll either need to deal with twice the work or use a server-side solution, both of which are more expensive than a responsive site.
  • Mobile devices aren’t a single screen size — It’s ironic that what was once the greatest strength of M-dot sites is now its greatest weakness. M-dot sites are designed for a specific screen size, but mobile devices range from 320×240 for some smartphones up to 768×1024 (and beyond) for tablets. It just doesn’t make sense to serve the same layout to all those screens.

Add them all up and you start to see the cracks.