<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nenad Grujicic on Medium]]></title>
        <description><![CDATA[Stories by Nenad Grujicic on Medium]]></description>
        <link>https://medium.com/@nenad.grujicic?source=rss-2f233a8ac952------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AhUw2ta8iL4kmiljJn5S8A.jpeg</url>
            <title>Stories by Nenad Grujicic on Medium</title>
            <link>https://medium.com/@nenad.grujicic?source=rss-2f233a8ac952------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:35:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nenad.grujicic/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Traveling through time is what you are here for.]]></title>
            <link>https://medium.com/@nenad.grujicic/traveling-through-time-is-what-you-are-here-for-7de989e1e5ca?source=rss-2f233a8ac952------2</link>
            <guid isPermaLink="false">https://medium.com/p/7de989e1e5ca</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[nostalgia]]></category>
            <dc:creator><![CDATA[Nenad Grujicic]]></dc:creator>
            <pubDate>Tue, 19 Mar 2024 10:23:25 GMT</pubDate>
            <atom:updated>2024-03-19T14:47:55.235Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2008, almost every website had a &quot;beta&quot; tag next to its logo in the header and was inspired by the Web 2.0, Flickr-ish design language. If you wanted to prove yourself even further as a real player in the web game, you had to add a &quot;hosted by mt&quot; (Media Temple) badge in your footer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2c-Qni8sWIpwCXpMmYG_3g.jpeg" /></figure><p>It was a period of Flash to HTML/CSS transition, and I was a designer and a part of the core team at Saturized Studio. Saturized was the first serious and well-established digital design agency based in <a href="https://en.wikipedia.org/wiki/Novi_Sad">Novi Sad, Serbia</a>. Mainly focused on Flash development, Saturized won several recognitions and awards (FWA was one of them) and attracted many international clients.</p><p>I have had the opportunity to work on projects for big names and agencies. Google, Toshiba, and 20th Century Fox are some names that reached out to Saturized for cooperation.</p><h3>But this story is not about those projects; it is about internal ones that we, as a team, believed in.</h3><p>In 2008, Facebook had already started dominating the social networking space. MySpace was fading out, Twitter was taking off to the stars, and Last.fm was there to show your favorite bands or discover the ones (a year or two later, Apple tried to steal Last. fm&#39;s crown with their Ping social media platform — you remember this one?)</p><p>My Saturized colleague and friend <a href="https://bajazetov.com/">Goran</a> had an idea and vision for a new social network platform. <a href="https://www.linkedin.com/in/zoranusancevic/">Zoran</a> had a strategy, and I was there to put identity, user experience, and interface design together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qhh89BwOVtfkkXT5euKtw.jpeg" /></figure><p>The social network was called Historide, which already implies its purpose — to ride through your personal history. The idea behind the platform was to create a safe space, similar to a vault, where you could add significant events from your life. The network would then serve as a time capsule for you to revisit these memories later. Of course, a social media component was present, which allowed you to share your events with others.</p><p>The platform encouraged users to create events based on memories, old photos, and diaries from before the Internet and social media.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z6VrYy1br000JKvPQDUDHw.png" /><figcaption>Post Creation</figcaption></figure><p>As I browsed through my project folders and checked Historide&#39;s PSD files, I was blown away by how well-structured, defined, and developed this project was. Folder structures, layer organization, naming, UX prototypes made as animated GIFs, sprite PNGs, notes… damn! I have a feeling that would be a project for itself these days.</p><p>Tools like Figma and features like components, developer exports, or inspectors did not exist back then. We only had Adobe Photoshop CS3, and that was it!</p><p>Macromedia / Adobe Fireworks was an excellent tool for web design. It handled both bitmap and vector design well. Preparing, slicing, and exporting components was easier and faster, but for some (still unknown to me) reason, it never became a &quot;default app&quot; for designing web interfaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-VdIKN_0MUotAc-ZIuoJtg.jpeg" /><figcaption>Adobe Photoshop CS3</figcaption></figure><p>Adobe introduced a wonderful feature in early Photoshop CS versions known as Layer Comps. This feature is still available in the latest versions and has been a real game-changer at the time. Layer Comps enabled us to have multiple states in the same PSD file, which was incredibly helpful. It allowed me to keep several pages and UI states in a single file. Moreover, I used layer comps as a versioning system to effortlessly navigate through revisions and make desired updates without creating and documenting numerous files.</p><p>Nowadays, design tools guide users on how to structure and prepare assets, making it unnecessary to overthink or explore additional options.</p><p>However, when we developed our GUI library for Historide, there were no available UX/UI guidelines or some proven and established rules and practices on the Internet. Each studio developed its design methodology.</p><p>Looking back at Historide&#39;s PSD file containing UI components, I believe we had a good design methodology because even though it is 15-ish years old, it looks and feels similar to today&#39;s standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*23PRFnz28IYHBuGXytl12g.jpeg" /><figcaption>Historide&#39;s GUI Library</figcaption></figure><p>Historide was an excellent product, but the reason it never gained popularity is quite evident. When we launched it, the Internet became easily accessible to everyone, and people didn&#39;t want to spend their time discussing the past. Instead, they preferred to share their present with others, and Facebook was the platform for that purpose.</p><p>Our time-traveling platform was online for a short period without making a significant impact. However, it made us stronger and more experienced as a studio. We tested our strengths and limits this way and proved that we could easily jump into similar projects for our clients in the future.</p><p>On a personal level, this project was a design goldmine for me. I learned a lot, and some of those lessons are still present in my workflow today. Additionally, Historide added much value to my personal portfolio, which I launched in 2011, and found its way to an <a href="https://liangzhang.co/">incredible person</a> who reached out to me. That&#39;s how I started working with <a href="https://www.hugeinc.com/">HUGE INC</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gvSmtzfDelbXIYwcSD2hjg.jpeg" /></figure><p>…. and that&#39;s pretty much it. I would like to add that 2008 was a great — I could say a special year! Kanye&#39;s 808s &amp; Heartbreak and Lil Wayne&#39;s Carter III were burning hot. &quot;Emo music&quot; slowly started transitioning from distorted guitars into distorted electronic music, later known as Dubstep, and I&#39;ve put together my first Hackintosh based on Intel Q6600.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fQnU0x4qECsBOL0HvkHx2w.jpeg" /><figcaption>Kanye&#39;s &quot;Amazing&quot; from &quot;808&#39;s &amp; Heartbreak&quot; is still my favorite Kanye song, and to be completely honest with you, Young Jeezy killed it on this track. 🫡</figcaption></figure><p>I want to tackle one more thing that somehow inspired me to put this story together. And that&#39;s Apple&#39;s Journal app. That app sneaked into my iPhone. I don&#39;t have an idea when and how. I guess one of the iOS updates introduced it. And guess what - I love it.</p><p>Journal really knows how to put together important life events for me by combining vital information found on my device. The app will combine a couple of nice photos and videos, including date and time, location, and people, and create a nice title for the post. I can provide more info or notes if I want, but even if I don&#39;t add extra details, the post/event still looks great!</p><p>This somehow reminded me of Historide, and I can see the Journal app as a one-stop place to explore my life from the past in the best possible way. And since I&#39;ve used the word -life, somehow, I think there is an opportunity to bring the iLife brand back to life. Imagine merging the journal and the photo app into one — to me, that screams <a href="https://en.wikipedia.org/wiki/ILife">iLife</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HT0JIW8q-q2shR8wbd7Ytg.jpeg" /><figcaption>PS. I hope the Journal app will find its way to desktops as well.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7de989e1e5ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first UX project. It was invisible and happened in ’99.]]></title>
            <link>https://medium.com/@nenad.grujicic/my-first-ux-project-it-was-invisible-and-happened-in-99-1c50a7e75621?source=rss-2f233a8ac952------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c50a7e75621</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Nenad Grujicic]]></dc:creator>
            <pubDate>Thu, 14 Mar 2024 09:23:08 GMT</pubDate>
            <atom:updated>2024-03-15T09:14:59.283Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>I was lucky to be the first in my school to get a CD burner. It was the Plextor model with a caddy box where you would insert a blank CD and then push it inside the burner like it’s a 5.25 -inch floppy. I can’t remember the model name, however.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xI5A4r7jTK34vl2tB_556Q.png" /></figure><p>At the same time, mp3 format started showing in the wild, and you guess the rest of this story. Many of my friends asked me to burn some mp3s. You know, 650 MB — 150-ish songs, good deal. I never had that entrepreneur mindset (25 years later, it’s pretty much the same), so this story is not about burning eMuled songs and selling them; this story is about my first UX project.</p><p>Ok, so what was the problem to be solved? Everything sounds straightforward: get the songs, burn them as data, give a CD to a friend, the friend inserts the disc and listens to music. Sounds good.</p><p>But there were many obstacles. The first and most significant thing is that the Personal Computer was still the niche and unique thing in houses. There were many technical limitations to playing mp3s. Operating systems didn’t have decoders preinstalled, so that was the biggest one; CD reading speeds (1x/2x) were also the issue. Even a simple thing like having software to play mp3s (read Winamp) was tricky. Internet connection was an uber-rare thing, and getting an app like Winamp was an extra task.</p><p>So burning a disc was just a half job done because most of the time, friends would call me to go to their house and set up their machines to play those CDs.</p><p>I started including an extra folder with all the required software to make my friends’ lives easier (mine as well). Fraunhofer mp3 codec and Winamp were essentials. Also, I would include a text file with a couple of sentences on how to install them. This sounds good on paper, but this made things even more complex in real life. Sometimes, people already had codecs installed, so sideloading a different one would lead to crashes, muted sound, or, even worse, completely stopping their Windows 95 from booting. In the end, instead of setting up their machines to play some music, I would be the one to go to their homes and fix them.</p><h3>Let’s move on to the topic of UX design.</h3><p>I stumbled upon autorun maker software from demo discs included with my favorite PC magazines. The autoruns were small programs that would automatically launch once you inserted a CD into your drive. You might remember them — when you inserted a game CD, for example, it would prompt you to install DirectX and then install the game. You could also access some extra promotional material and demo games from the same publisher.</p><p>I have spent much time designing the perfect one, with huge shiny buttons. The first button would say, install codec with an extra text, not do it if the codec is already present. The same was true for the Winamp installation. PNGs and transparencies didn’t exist in this era, so having a round corner button would involve adding masks to achieve the rounded effect. Once I had a perfectly designed autorun, I quickly realized that this is still the same thing as including a folder, and it doesn’t fix the problem; it just looks nicer.</p><p>The answer was to automate this process entirely. Since I had experience making MS-DOS Batch files, I made a .bat script that first inspects the machine to see if the codec is installed. If not, it would start the installation from the disc. After this operation, the same would go for Winamp; if it’s not present, it would be installed automatically. The last thing was automatically launching Winamp and importing an m3u playlist with all the songs from the disc. I removed all the buttons from the autorun and kept only the one that said — Play music.</p><p>This was the biggest test for me. I was looking at my design, and I knew it. I could kill it entirely and just run the script upon CD insertion. And that’s what I’ve done; I removed it and avoided that extra step of clicking the nice-looking button. Instead, my friends would insert the disc, and without thinking about what’s happening in the background, they would be presented with Winamp and their freshly burned music playing.</p><p>I sacrificed my visual design in favor of simplicity and ease of use, and yep, I was pretty sad because of that (especially for young me overhyped to show my design skills). Still, at the same time, I got something much better: a bunch of comments that discs just work.</p><p>Back in the day, I didn’t have an idea that 20-ish years later, I would write about my adventure to simplify music listening for my school friends. But here I am, still doing pretty much the same thing today: offloading heavy and not-so-interesting stuff for users and presenting only what the user needs in a good-looking way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c50a7e75621" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>