4

Ask DN: Where Do You Keep Your UI Experiments?

6 years ago from , UX Designer at Gather Technologies

I always have lots of extra versions of UI I'm working on that I'm working on. Sometimes I show these to the team/client, but often I just want to keep them around to show that either a) I tried a solution and it didn't work for x reasons or b) as fodder for potential future improvements.

We try and keep a single file for each section of the app to stay organized. I'm just not sure how best to save these tidbits without a huge loading problem/some sort of historical record of what each is and why it's still around.

7 comments

  • Lee HordLee Hord, 6 years ago

    I find InVision is great for this, it keeps a copy of each screen revision which you can then browse using History mode. The only thing that's lacking is a way to tag old revisions.

    2 points
    • Adam HaasAdam Haas, 6 years ago (edited 6 years ago )

      I agree. I have been doing this and it integrates really well with Sketch.

      For UI prototypes I save my code to either codepen.io or github.

      2 points
  • Eren Emre .Eren Emre ., 6 years ago

    For us, there is a master file (e.g. Core.sketch) and multiple files for experimentations.

    So, whenever we work on a new feature for our product, we create a new file for the feature (e.g. Search-v0001.sketch). The version number increases as we make changes & iterate (e.g. Search-v1019.sketch).

    As soon as we are happy with the feature, we add it to the master file. This way we know where the final version is and can keep an archive of how we got there.

    PS. All files are kept in Dropbox. Master file is also kept on GitHub, so no one can ruin someone else's changes.

    1 point
  • Robin RaszkaRobin Raszka, 6 years ago

    Github

    0 points
  • Joe Blau, 6 years ago

    I was just thinking about this over this past week. I was actually going to build a GitHub site with all of my UI experiments with sample code for a style guide I'm developing.

    I have code examples for parallax on boarding, custom image blur buttons, transition gradient backgrounds, color schemes, drop shadow custom buttons, invisible navigation bars, relative luminance color extensions, font weight and size presses, typographical formatting extensions, gesture visualizers, and a bunch of other UI elements.

    A lot of my stuff is code and they can be turned into reusable components to be used on client work if I were to ever go independent again but right now my stuff is scattered all over the place.

    0 points