Afnizar Nur Ghifari
afnizarnur.com
Afnizar Nur Ghifari
@afnizarnur.com
🇮🇩 Designer, builder, photographer, and everything-in-between. Always exploring and learning new things.

afnizarnur.com
I've got it working with Spotify's API to pull actual album tracks into designs. Still ironing out some CORS stuff, but the core feature is live and ready for you to play with!
February 23, 2025 at 4:24 AM
Building accessible components is always worth it, even if you're unsure about your users' needs. With AI lending a helping hand, it's easier than ever, just remember that MANUAL TESTING is still essential!
January 15, 2025 at 5:57 AM
Here the repo that still wip, need to improve on the docs how to contribute

github.com/afnizarnur/d...
GitHub - afnizarnur/datapaw-library: A growing collection of data to generate realistic content, powering up the Datapaw Figma Plugin.
A growing collection of data to generate realistic content, powering up the Datapaw Figma Plugin. - afnizarnur/datapaw-library
github.com
January 14, 2025 at 3:09 AM
The process that I come up like this: Data is placed in a public GitHub repo, the plugin just fetch data, then we can generate. Done.
January 14, 2025 at 3:09 AM
Adding new sample ata should be simple and also user can contribute to it if they have interesting data to share to the community.
January 14, 2025 at 3:07 AM
Why replace? The problem is faker.js taking a lot bundle size if I want to add more data to it. Also, maintainability!
January 14, 2025 at 3:07 AM
#buildinpublic means sharing both wins and lessons learned. I'm also publishing design artifacts here so I can remember what things I've built and where I've failed 😅
January 7, 2025 at 2:14 AM
Lesson #3: While innovation requires some educated guesses, knowing when to step back and reassess is just as important as pushing forward. Sometimes pause > persistence. 🎯
January 7, 2025 at 2:14 AM
Lesson #2: When tackling complex features (especially ones that eat up more than 3 hours of after-work coding), break that beast down into smaller chunks instead of trying to do it all at once.
January 7, 2025 at 2:14 AM
Lesson #1: Plan things out properly and really think about how designers will actually use the feature day-to-day.

Looking back, low usage numbers show I probably should've chatted with potential users first.
January 7, 2025 at 2:14 AM
Reality check: things got pretty messy with tons of edge cases popping up, making the whole data generation thing a bit of a HEADACHE to maintain.

Not exactly what you want in production! 😅
January 7, 2025 at 2:14 AM
But here's the thing, after giving it some serious thought, I've decided it's time to let this one go.

Why? It wasn't quite production-ready because I might have jumped the gun a bit on planning. 🤔
January 7, 2025 at 2:14 AM
When I first launched this feature, I was pretty excited! I mean, who wouldn't be? It was something competitors didn't have, fancy interconnected data that you could control with conditions.
January 7, 2025 at 2:14 AM