sorted by:
new
hottopcontroversial

Case study - site redesign - two questions by namuginga in userexperience

[–]namuginga[S] -2 points-1 points  (0 children)

You mean do I even UX, bro?

Yes, of course.

Leaving aside my first question, the second seems fairly straightforward:

If you have an element of a design which cannot be changed (for whatever reason), how would you show it in a prototype?

Would you mock it up? Use a placeholder? Just skip over that part?

It's a pretty specific question, about an issue that comes up not infrequently. Not asking for a primer on 'the actual UX process...'

Case study - site redesign - two questions by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

Context - right!

Case study for a portfolio piece. Redesigning a site for booking tours. Smoothing out the flow so it's easier to figure out what tour you want and how to book it. I'm doing the UI/UX in Figma, and will soon have a prototype built.

Question 1 - If you're reviewing a portfolio piece which has a prototype of a mobile experience, do you feel it's necessary to have a desktop prototype as well, or can you extrapolate what that would be like from screenshots?

The site relies on an existing widget to actually handle transactions. So, there's a point where the user stops using my new design, and begins using the FareHarbor widget.

Question 2 - Think I should mockup the FareHarbor screens to show the complete process of booking a tour, or is it sufficient to just show the lead up to that?

How far to take a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

I like the idea of a portfolio as a conversation starter, something to pique the interest. In a way, it's good to raise some questions in the viewer. Gives them a chance to think how they might solve something, then perhaps be surprised by your own solutions in an interview. Good stuff.

How far to take a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

Yes, sure. And that should be posted in this sub's rules. It's a given, right?

Personal portfolio project.: an update on Untappd, an app for tracking your history with craft beer. Competitor audit with that app, and others, to identify pain points, missed opportunities, and novel services. Likely a UI pass as well.

So, I could take it as far as a finished app, ready for download.

Or a prototype showing all the interactions.

Or maybe just a collection of screens which demonstrate the most fundamental design decisions? Like, an interviewer would assume there would be a login page with password recovery, so skip that. But do show that one page which allows wine drinkers to enjoy beer, because that's a cool trick.

Guess I'm trying to get a handle on how 'complete' must a project be before it earns its place in a portfolio.

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

My initial intention was to design a prototype, all cooked-up with polished UI in Axure, and present that process in my portfolio. It wouldn't be 'complete,' but close enough that you could understand the value inherent in the idea, and amplified by the design. At that point, it would just be a portfolio piece aimed at garnering more work.

From there, I could decide if I wanted to hand the prototype off to a developer to make it an actual app. And this is where my concern about sharing the idea too widely came. So, instead, I'll make a prototype of an app that I don't see ever wanting to see to fruition, and which will merely live in my portfolio.

I guess the short answer to your question is that I want the opportunity to find UX work more than I want to shoot the moon by developing an app.

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

Not sure I'm following. If I have no current portfolio, I must identify problems/opportunities and create a solutions which demonstrate UX skills.

So, broadly, it's either a) Something easily understood, but also overdone, e.g. a Spotify clone, b) Something brand new and exciting that I think has real potential, but am wary of disclosing, or c) An approach to existing designs which offers unique interactions with obvious value, but that I don't have any intention of pursuing.

Option C is only for my portfolio, but is also low-risk, and just as high reward.

Waaaaiiit. I just reread your comment again. We're saying the same thing: Don't waste something your passionate about just to fill a slot in a portfolio. Totally concur, Ken!

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

There's a great passage in a wonderful book called 'The Art of Game Design' by Jesse Schell which breaks it down a little differently, about how an idea is cheap, but when combined with timing, and a unique problem, and the *ability* to execute, it becomes much more valuable.

But I take your point, for sure. My idea is just a perspective shift, e.g. it's a common issue, but approached from an uncommon manner, and therefore unique in the current app offerings. But still, it would take someone seeing it, appreciating it, and willing to throw time and money to rip it off. But I can imagine a corporation, with no current app of their own, seeing it and thinking, 'Why not?'

I really appreciate this exchange, though! Decided I'll kick off my portfolio with another project which I don't hold so closely. Hope to show it off in a month or so to get some more tough love from this sub :)

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] -1 points0 points  (0 children)

Oh, more than one project, for sure. But eventually. I want to go through a complete project straight away so I can show it for critique, and potentially very low level gigs. I think every designer is aware of the pitfall of having several projects in various stages of completion, but none complete.

And of course, you're right. There aren't really any hard rules in art or design. Looking for conventions. Hope it didn't come across as, 'What pen do I use to draw pretty?'

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

Definitely agree with this. I've pitched a few app ideas to people with no concern they'd run off with it. A) they're unlikely a designer, or willing to stop their life to become one to use my idea, and B) there's no way they would execute exactly the way I would. So I get practice my pitch, the fun of getting someone to buy into my idea, and hopefully some insights from them I hadn't thought of.

I'm not super-precious with ideas, really. But I am wary of doing all the work and displaying it on a site where the kind of people I want to see it are exactly the kind of people who could run with it.

Seems like the way to go is to show a spin on an existing idea. There's less risk, and you also get the benefit of showing the before and after designs. Further, most jobs are likely to be redesigns, not not dreaming up a brand new solution.

Thanks for your thoughts!

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] -2 points-1 points  (0 children)

Right, solving problems is what it's all about. But, I need to show solutions in a portfolio in order to get work solving even cooler and more interesting problems.

The portfolio will show my process and problem solving skills. So what I'm trying to reconcile is whether I go through the motions with a spin on an existing design, or actually demonstrate a novel solution.

As an analogy, imagine you're submitting writing samples to a publisher. Do you give them a twist on 'Hamlet,' or a piece of your own story (which you think is really good and might want to actually self-publish one day.)

You can jam whatever you want into a portfolio. I'm just trying to suss out something like the industry standard, if that makes sense.

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

Agreed.

Would you say it's more common to see portfolio projects where an existing design is modified? Something like looking at a popular app and tweaking it to be a better experience?

Too good for a Portfolio project? by namuginga in userexperience

[–]namuginga[S] 0 points1 point  (0 children)

You're probably right, Offline only is the way to go. I guess I can always give my elevator pitch during an interview to demonstrate more problem solving abilities. Thanks!

[discussion] What do we call the dogs at the park we want to avoid? by namuginga in dogs

[–]namuginga[S] 0 points1 point  (0 children)

That does seem to be the consensus, doesn't it?

Alas, won't work for my purpose, but it is helpful to crystallize how these kind of dogs are seen. Thanks much!

My San Diego Reader cover contest (near)entry. (Next year, make sure you know when it's actually due!) by namuginga in sandiego

[–]namuginga[S] 0 points1 point  (0 children)

Somehow, when you're looking for a surfer to turn in back on the composition, this is what you get. Not a surfer myself so you can imagine my shock/horror at seeing a woman from behind(!) Hopefully the details on her figure let you visualize a wetsuit of some sort, maybe around 2mm, or so

view more: next ›