So I upgraded to Apple’s Mac OS Big Sur. I have to start out by saying that I feel Apple has been slipping in recent years with basic usability. The whole flat UI thing sucks not just in my opinion, but also in usability testing I have done with designs that were “flat”. Also I am not sure who started it, but between Apple, Google, and Microsoft all hiding scroll bars, it’s really a annoying trying to notice when there may be more on the screen. The first thing I look for now when updating OS is the option to force scroll bars to be visible.
Having said all that, I have to say that I generally like the look and feel of Big Sur and also liking some of the new features. The finder windows do feel cleaner and more refined. The new control center is interesting, but I have yet to really use it. There are new privacy and security measures which is good to know that they are improved. Overall though it seems just OK. I am not wowed by anything just yet, but also there have been no major glitches as well. I do really appreciate that Mac OS upgrades are free now. If there is anything else that pops out over the next week, I’ll be sure to make note here.
It’s been said before, the future is coming faster than we think. This is true now more than ever as the advent of “AI” and robotics automation is beginning to seriously take hold. I put AI in quotes because it is still far from true artificial intelligence. It is because of significant increases in computing power and networking that increasingly complex algorithms can be run. Which gives the appearance of “intelligence”, but the reality is this is not true intelligence yet. While a machine can learn, it still has to be cultivated and corrected and ultimately it is not really thinking.
Anyone who has engaged at length with Google Home, Amazon’s Alexa, or Apple’s Siri knows that there are plenty of limitations. As great as they are for somethings you very quickly run into problems for anything that is not yet factored in their algorithms and resources they pull information from. Having said that, they and other AI driven technologies are gaining traction in business. I know that there are many others predicting the same thing I am here…
So I have been using repeaters in a couple of prototypes in Axure. Repeaters allow creating a single element that then is linked to a data table and will repeat content based on how many rows are in the data table. This can make it much easier to automatically simulate a list/grid of search results with real content. You can also then add controls to filter and sort and paginate the list. There is also the ability to dynamically load images from an external source. All of this awesome functionality was making it fun to build out some prototypes that I had intended to do some remote/unmoderated usability testing.
Unfortunately, complex repeaters (6+ columns, external images, links/refernce pages, etc) with more than around 12 rows can substantially slow down the loading of a prototype in a browser. It gets even worse from the axshare server. Also, having more than 1 repeater widget on a page can also slow down a prototype to make it basically unusable. So I fell back to using dynamic panels with states to represent more limited simulation of filtering.
There are some ways to optimize repeaters including using the pagination functionality to load a smaller set of content. However, even after this optimization I still found my prototype pages with repeaters taking upwards of 8-10 seconds to load locally. Viewing pages from the axshare server which can be slow on its own, was often pushing 20+ seconds to load a page. For all the power they offer it was a big dissappointment to not be able to use repeaters in the prototypes for the usability testing. I am still looking further in to how to optimize things. I think it would be helpful if we could make a repeater load asynchronously and perhaps have a place holder image or group of elements.
AxureEx can be found here:
And the downloadable file is here:
Credit to Sam Hepworth
Spending some of my time off exploring microdata and html5 more in depth. If the semantic web is going to finally gain wide adoption microdata is going to be the catalyst. Unfortunately as easy as it is, it still involves a some effort to add microdata to your code. Still it is a million times easier than XML or other semantic formats.
Unfortunately, I think performance will still be an issue in actual implementations. Microdata is still fairly verbose and also referencing the scope/schema from a third party server may be a problem for some high traffic servers. Adding microdata to your mark-up can easily double or triple the size and there is always the latency issue of referencing a third party server.
These were the sources I was reviewing;
More and more web designers are seeking to dispel the notion of the browser fold. Yet there is still the reality that users can not see all of a page’s content if it is taller than a browser window and they will potentially leave the page before discovering the additional content. There is often an email sent from the CEO or other senior manager stating that they want some graphic or link moved above the fold. This typically ruins the layout or requires major reworking to get things to fit.
I guess I should back up a bit and explain that the fold is an invisible line where the content of the page is not visible below the bottom of your browser window (and/or to the right side if there is also more content than can fit into one screen horizontally). It is borrowed from the print world where certain print formats such as newspapers and brochures are folded. The content that was most important appears on the front page before the fold to be sure that the consumer would notice it.