Farhan Ramadhan
2 min readNov 24, 2020

--

Thanks for your kind words and your feedback to keep the discussion alive. I can even understand the bigger aspect of the portfolio itself. So thanks to all of you guys.

But keep in mind that:

1. I mainly talk for new designers that don’t know how to present their portfolio – and usually, they also don’t have much knowledge to know about coding or web deployment. Which will take times for them to learn first, and try to implement it for their portfolio.

2. It’s unfair I guess if we try to compare it with a real web portfolio. Because when you want to build a web portfolio, there are a lot of things that you need to understand first – and there is some cost that you need to pay to. So I think it would be fair if we compare it with Behance, Dribbble, and Notion.

3. Figma prototype isn’t built for this type of situation. So this experiment mainly tries to break the notion of Figma prototype usage. I believe by creating your portfolio in Figma, it will also create a demand, and when there is a demand, there is a supply for it. So by moving forward with the Figma prototype, hopefully, the Figma team will start to look after the issue and solve it in the future. Because Figma is a community-based design, I believe in the future they will have something to improve this kind of situation.

So yeah even though there are some drawbacks that I agree with. But I must say it’s a good bet to go with Figma. At least for me haha. But yeah, feel free to share your responses. Cheers!

--

--

Farhan Ramadhan
Farhan Ramadhan

Written by Farhan Ramadhan

Product and UI UX Enthusiast. Together designing the future with technology.

No responses yet