Download Buttr: https://itunes.apple.com/us/app/buttr/id1033885935?mt=8
Sade Olutola
š
trying on a metaphor
Game of Thrones Daily
ojovivo

Origami Around

romaā
Today's Document
šŖ¼

blake kathryn
Noah Kahan
cherry valley forever
Not today Justin
Misplaced Lens Cap

ellievsbear
No title available

ā
DEAR READER
No title available

⣠Chile in a Photography ā£
seen from United States

seen from United Kingdom
seen from Russia
seen from Philippines
seen from United States

seen from United States
seen from Mexico
seen from Germany
seen from United States

seen from United States

seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States

seen from United States
seen from United States
seen from T1

seen from Malaysia
@theuxfiles-blog
Download Buttr: https://itunes.apple.com/us/app/buttr/id1033885935?mt=8
The Cobweb, contād
When I tweet or post on Facebook I rarely think, āWill I want to access this in 10 years?ā or āIs this going to haunt me for the rest of my life?ā So much of the internet is ephemeral. The internetās emphasis on speed and access nudges me away from considering the web as a tangible document with longevity.
Thatās why Iām glad to see the archivability of a website is becoming a serious consideration for developers and designers who want to create the best internet products. Alongside accessibility and performance, archivability is one more factor that the internet community must juggle. According to the Stanford University Libraries, the term archivability is āthe ease with which the content, structure, functionality, and front-end presentation(s) of a website can be preserved and later re-presented, using contemporary web archiving tools.ā
Still, there is a current trend in web development to build web applications in React (sites are running primarily JavaScript with little HTML). How does the prevalence of JavaScript affect the overall archivability of the web? Because many internet archivists and tools rely on HTML to store data and pages, the rising dominancy of JavaScript calls into question our current means of archiving. Perhaps The Internet Archive is ill-equipped to fully preserve tomorrowās internet. They themselves recognize that they can not fully document dynamic pages. On The Internet Archiveās Frequently Asked Questions, it says the archive is unable to save a siteās original functionality if the site contains interactive elements. Do we need to reevaluate the solutions that have been developed to combat the ālink rotā and internet decay we read about in The New Yorkerās piece āThe Cobwebā by Jill Lepore?
A lot of this conversation is a bit over my head, but I find the idea of preservation and archiving the internet fascinating (especially after last weekās readings). I never really thought about how the Internet is constantly shifting and whether or not itās too dynamic to be saved. I stumbled upon the discussion about JavaScript and internet archiving via my husband (who happens to be a front-end engineer using React on a daily basis). I asked him if he knew of any tech trends that could affect Library Science and the Information Sciences. He pointed me to the post āJavaScript and Archivesā written by Ed Summers. In the article, Ed Summers dissects the implications of building with JavaScript.
Ed Summers offers Twitter as an example of a JavaScript-heavy site that can still be archived. He also offers solutions for those archivists currently documenting the world wide web. He ends his piece on a practical and optimistic note:
āIf you are in the business of building archives on the Web definitely think twice about using client side JavaScript frameworks. If you do, make sure your site degrades so that the majority of the content is still available. You want to make it easy for Internet Archive to archive your content (lots of copies keeps stuff safe) and you want to make it easy for Google et al to index it, so people looking for your content can actually find it. Stanford Universityās Web Archiving team have a super set of pages describing archivability of websites. We canāt control how other people publish on the Web, but I think as archivists we have a responsibility to think about these issues as we create archives on the Web.ā
There are other reasons to implement JavaScript with care. According to Stack Overflow, approximately 2% of internet users in the United States disable JavaScript on their browsers. Even though this number is small, itās important to consider the needs and wants of internet users so we donāt adopt JavaScript with wild abandon. According to aTechCrunch article on programming trends, JavaScript is the most prevalent language used in the world. The newest version of JavaScript was released in 2015, which has cemented the language as one of the most modern and universal.
The past two weeks of class have sort of converged around the JavaScript/archive debate. When we read about the Internet Archive, I didnāt fully understand the limitations of what they were trying to do. When reading about the history of HTML for this upcoming class, I didnāt fully understand the side effects of the in-fighting to develop a web standard. It seems like some of the uproar over how the Internet should be built led to a reliance on JavaScript. Which leads us to where we are today: one thought leader in the space urging the community to dismantle a system built on JavaScript frameworks (i.e. Tantek Celikās post on JavaScript) while another (Ed Summers in āJavaScript and Archivesā) arguing for building better archiving tools.
Do you think it is our responsibility to build better archiving tools that account for all internet variations, languages, and trends? Or do you think the responsibility lies with those that build the web to consider archivability when they develop in an effort to save and maintain our collective information?
(P.S. The original article by Ed Summers was duplicated in a Medium group called āOn Archivyā that focuses on internet archiving as it applies to #BlackLivesMatter. Check it out here:https://medium.com/on-archivy)
When your annotations get a shout out
Collabāing with the hubby. UX and Engineer love
The Empathy Era
Two weeks ago, I felt a childhood rush of excitement for cardboard. When the Google Cardboard viewer from the New York Times arrived on my doorstep, I tore open its blue plastic packaging, downloaded the NYT VR app on my phone, and set myself up for some quality virtual reality viewing time.
After playing around with the app for a couple of minutes, I packaged the viewer back up, put it on my bookshelf and went out to brunch. I hadnāt even made it through a 1:44 minute-long video before setting it aside and going about my regularly scheduled life. Despite a desire to engage with this new piece of technology, I refused to pause my life to learn about someone elseās. My selfishness trumped my curiosity. Call me a millennial.
I like to think thereās a deep-seated wisdom of the other at the core of my being. Having been connected since adolescence to a wealth of information on the World Wide Web, my perspective is inherently broader than my parents. Even if this were true, thereās still an all-consuming resistance to empathize with others. Selfies, vanity, and egoism run rampant. Could the NYT VR mobile app save us from ourselves? Is virtual reality the harbinger of The Empathy Era?
A part of me hopes it is. I want to believe in the promise of the New York Times virtual reality app to transport me to another place. I see potential in it to free me from myself. Itās a lot to expect from folded cardboard.
I finally got to watch the full eleven minutes of The Displaced last week. Naturally, I was disappointed when I didnāt feel āpresent in these vivid locations, a virtual witness to these childrenās precarious lives,ā like Jake Silverstein, Editor of The New York Times Magazine, wrote.
While watching the virtual reality film, my phone dinged with text messages. Halfway through the video, while Hana was telling me about cucumber picking in Lebanon, I got a call from a friend (this doesnāt happen often).
āHeyā
āWhy didnāt you respond to my text?ā
āIām watching a video.ā
āOkay, well can you answer me?ā
āWhat did you ask?ā
āDo you think I can make it in New York?ā
āYes. I already said you should move here. Anyway, Iām watching a videoā¦ā
āOkay, can I call you later today and we talk?ā
āSure.ā
She never called me later that day.
Shutting down one of the first verbal exchanges over the phone Iāve had with my closest childhood friend in over a year, I returned to my virtual reality film so I could empathize with others: really put myself in their shoes.
As I twirled around my room with the Google Cardboard viewer pressed against my face, I followed three children through their struggles as refugees in a war-stricken world.
When the video finished, I didnāt feel transported; I felt displaced. Instead of feeing like a part of Olegās world, I felt removed from mine.
As seen on:Ā https://medium.com/@turkishdlite/the-empathy-era-b758d1e1f7a7#.kckry8hbk
Iāve run into a lot of conversational interfaces and chat bots. Recently, I talked with the UX Bear at uxchat.me. UX Bear is a casual way to engage with trending UX news. Iāve seen similar chat expā¦
Design - QA - UX Trifecta
Apple Watch
Itās been two weeks since I strapped an apple watch to my wrist and not much has changed. Every morning I wake up, take the dog out, strap the watch on, and prep for the day.
I went one day in the string of 14 without the watch and felt naked without it. Despite all the productās ābetaā flaws, Iāve grown accustomed to the soft ping and subtle pulse of its notifications. Even though it tells me to stand up when Iām already standing (this is annoying AF), I muster enough appreciation for it to keep the band fastened.
In an effort to make sense of this seemingly useless and frequently inaccurate gadget, hereās my attempt to evaluate the watchās interface and interactions according to Nielsenās five components of usability.
Learnability: Is it easy to perform basic tasks when first introduced to the design?
No, not really.
Efficiency: Are task easy to accomplish quickly once the design is learned?
Nope.
Memorability: Can users maintain proficiency and remember how to use the design?
Hmm, maybe?
Errors: Do users make errors often? How critical are the errors? Can users recover from their errors
Yes, but they arenāt critical.
Satisfaction: Is the design pleasant to use?
Yes.
All in all, I canāt wait to see how the apple watch will evolve. Oh, thereās the watch! Iāve been sitting too long and itās time to stand up.
UPDATE: Iāve completely stopped wearing the watch.
When you need to make room in your UI ...
The evils of UX
āWhat is a lobby boy? A lobby boy is completely invisible, yet always in sight. A lobby boy remembers what people hate. A lobby boy anticipates the clientās needs before the needs are neededā -M. Gustav on what it takes to be a lobby boy *cough* UX Designer *cough*
See also 5 Things UX and UI Designers Could Learn from Wes Anderson
To my fellow UXDI Jets⦠Read the fine print.
Trust the winds!!!
Final presentations!
Presentation day!
For the Instagram Prints team.
Only $200? Impossible!
Like a magic trick, truly great design is not something that is created with ease, but almost always requires more work than seems reasonable. A typical business-oriented designer wonāt take this path. An artist will. Decide to be that artist. The execution will be challenging. Jump the mental hurdle to magic. Donāt stop before you even get started. When designing something, consider āHow would it work if it were magicā and then work backwards from that until you come to a solution thatās possible to build.
Nathan Manousos (via itwashalcyon)
To prospective employers: "When you're ready, come and get it..."