menu

SpecFM

A network of designers and developers making the best podcasts, blogs, and resources for designers and developers.

Channels
Team

Redid my Personal Website

June 27, 2017 at 6:38am

Redid my Personal Website

June 27, 2017 at 6:38am

Hi Guys! I just redid my personal website and would love to get some feedback! Check it out here, http://abheyraj.com


June 27, 2017 at 3:57pm
Congrats! Is there anything in particular you're looking for feedback on? The case studies, the visuals, the layout?
  • reply
  • like
Without knowing the answer to your question yet, a couple things jumped out to me:
  • reply
  • like
1. The case study links have a nice animation in/out, but the way it's implemented breaks the browser forward/back functionality. This means that there doesn't seem to be a way to link directly to a case study and once you're in a case study you can't click back to return, swipe back to return (if on mobile) - the only way to go back is to hit the 'x'.
  • reply
  • like
2. The mouse scroll hint on the home page is gesturing in the reverse direction for me, since i have the default macOS scroll inversion on ;)
  • reply
  • like
3. The hover animations on the case study cards are pretty cool and visually interesting, but were a bit disorienting at first and made it harder to click in to view the case studies. One way to help this would be to turn that off, but if you really like the animations maybe you could make the whole card clickable to view the case study?
  • reply
  • like
Anyways, I'll wait on more context from your side - overall it's looking really nice. I didn't dig in too deep to the case studies yet though, so my feedback is a bit surface level right now.
  • reply
  • like

June 28, 2017 at 8:08am
Sorry for no context! I basically am looking for overall feedback in terms of a hiring perspective for freelance/full time positions.
  • reply
  • like
Regarding the hover animation. I'm personally a big fan and took me a while to get them to work. So what I'm considering is to make the whole block clickable and ditch the view case button. I know that you didn't read the case studies, but do you think the content was structured well?
  • reply
  • like

June 28, 2017 at 3:42pm
Sounds good re: the case study blocks being clickable :)
  • reply
  • like
Re: case studies - i'll dig into the Lisn one if that works, and maybe some of this is relevant to the other case studies. Overall it feels like a good start - you opened with a story that described why this was important for you to build and how the idea came up. That's useful context. But between your second and third paragraphs we skip a massive part of your work and process:
  • reply
  • like
"We started out with a basic MVP of the product which we launched in April 2016. Our idea was to just have a Chat and Library where you can revisit tracks that were sent to you by friends."
  • reply
  • like
One of the things that feels useful before there is to explain why you made the decisions you made in building the MVP. Why did you only start with Chat and Library? Why was it important to revisit tracks that were sent to you, versus a more ephemeral or feed model? Did you talk to other people who wanted something like this? What are competitors in the space doing (Spotify, SoundCloud, Apple Music, etc) - or better: what are they not doing that made your thing so awesome. (Note: if this was just a side project, I think that'd be good to call out? The way the case study read was that it was a company you had started, but maybe that's not right?)
like-fill
1
  • reply
  • like
Then your next paragraph:
  • reply
  • like
"We got a lot of feedback from the MVP and started thinking about what a finished product would look like. Initially, we thought that the music experience could be split into three parts, Discovery, Archiving and Re-visiting. With that in mind, we created 3 basic tabs in the app, one for chat, one for the library and the last for a solo player in the app to revisit music you've already shared with friends. "
  • reply
  • like
Agin we've jumped over a huge piece of the design process :) How did you go from MVP to finished product? What was the feedback on the MVP? What did you learn when you saw people using it? What were clear areas to improve? Why did it become important to split the app into the three sections you listed?
  • reply
  • like
Overall note there: I was left with way more questions about how you think as a designer and what your process.
  • reply
  • like
Next you jump to:
  • reply
  • like
"With all of this baked in, we launched Lisn in August 2016. And lo and behold! We were number 2 on Product Hunt and that lead us to be featured on Tech Crunch! Woohoo! "
  • reply
  • like
Which is awesome - congrats on launching and getting to the #2 on PH! But again, I'm left with so many more questions: what kinds of feedback did you get? Did your changes to the 3 tab system work? After shipping the second version, is there anything you felt like you would have done differently given more time and resources?
  • reply
  • like
This paragraph was super good because it explains feedback you got, describes the problem, and then you show how you solved that problem:
  • reply
  • like
"Another one of our major feature requests was queuing up multiple tracks for live listening. It was too hectic to keep on opening the phone and picking a track. This made the experience much more laid back and extended the overall listening sessions. "
  • reply
  • like
More like that!
  • reply
  • like
"After thoroughly studying user behaviour over time, we realized that the app needs a better library as well as a separate solo listening experience. How do we become our user's primary app, rather than Spotify or Soundcloud?"
  • reply
  • like
That paragraph started to scratch the surface of what I mentioned earlier - what kinds of feedback did you get? What were you learning? Why did you want to become a primary music app rather than an extension to Spotify/SC? Would creating a separate solo listening experience fragment the apps functionality and distract from the original problem you were trying to solve (real time sharing)?
  • reply
  • like
And then at the end, things end suddenly. Which is totally fine, but I felt like there was more you could have talked about. More about what the next steps were, what you learned, what you would have done differently if you had more time + resources. All of those things feel useful as a post-mortem kind of exercise and offer a lot of insights into how you think about building products.
  • reply
  • like
Show more messages