
đź‘‹ Oi, mga repapips, Brian Dys here! I love music, photography, and creative stuff like UX design and art. This is a place where I collect my thoughts and works. Apart all these, I’m Jaycelle’s better half and Bryce’s dad. 🥰
My money allowance in college—they all went to the photo shops for films and development. I started shooting black and white because they were cheaper at thirty–six shots, 200 ISO. It was sufficient back then—having thirty–six in the roll. Having a couple or more rolls would take months to expose.
Only precious moments were captured and the moments captured became captivating.
Etched in my memory until now was the dream I had of having a digital camera—yes, unlimited shutter clicks. It was a feeling—no, more like a longing—in my waking life that manifested itself one night. I woke up in frustration—of only dreaming, of not having.
Imagine the possibilities was the only thing I could think of. Imagine the possibilities of never having to curtail my favorite moments.
The results were endless offshoots—photos that were not five–star material yet not fit for the trash bin either. So they get exported into a lower resolution for easier archival.
Maybe one day, future me would match the feelings of those blurred and unkempt slices of life. Scarcity, then, would not only be about quantity but about time incapable of rewinding.
What a great news for the start of September—I received confirmation that NTT is already in the WP Theme Directory.
Recently, the team is delving into gamification—ultimately, towards user engagement. Glad to have encountered the ARCS model of instructional design which is similar to the engagement loop.
ARCS stands for: Attention, Relevance, Confidence, Satisfaction—which could also be an engagement loop in learning.
I still could not wrap my head around the whole idea of frames. However, I did like the structure that was described in relation to linguistics.
We could notice the structure—from the detail towards the bigger picture. Patterns like these are also relevant to Information Architecture.
How about applying the DRY Principle in a user interface?
One method is by using a single element to have multiple functions. In the case of a <label> and a placeholder attribute in a <form>, we could simply use the <label> to be the only label of a particular field—as opposed to having two.
Besides, their main functions are to tell the user what field it is and what it expects as a user input—so why not optimize it?
Regarding its accessibility, please read an 2010 article from WebAIM and a recent one from Smashing Magazine.
Here’s a quick PoC. Try focusing on a field and see the label move.
<p class="codepen" data-height="300" data-theme-id="1820" data-slug-hash="YjowRP" data-default-tab="result" data-user="BrianSahagun" data-pen-title="Using
Ideally, it is 48 x 48 pixels. However, there are elements that needs to be smaller in relation to other elements with it—with this consideration, we could go down until 32 x 32 pixels.
In order to show cohesion and relation between two UI elements, we could use proximity—place the element near each other. However, when there are more important considerations like if space won’t permit one element to be there, we could use motion to cue that those two elements belong together.
The elements in relation to the user’s “now”.
Elements that are there only when you need it and also there when you thought you didn’t need it.
Numbers 3 and 4 fall under Relevance.
The outcome most teams are aiming for is a change in behaviour. The outcome you want will depend on your business or organisation: it might be selling more dog food, getting people to sign up to a monthly donation to your charity, or opting for mediation over court in their separation. Source
When deciding the number of characters an item could have, consider thinking about it being in other platforms.