Skip to main content

My 2 cents on the post: "Facebook IPO Post Mortem - Killer - but not for the reasons you think!"

Context: Facebook IPO Post Mortem – Killer – but not for the reasons you think ! I won't speculate at the reasons for Facebook's low IPO, I just wanted to add some positivism to reason number 4 stated in the blog post; the fact that more users are going mobile.

Yes I believe it is a fact, but I also believe that screen real estate will stay king for a while. Some environment settings require screen real-estate, e.g. at your office. Its difficult for me to imagine that in the near future you would do all your work on a small screen. Research shows that smaller screens lead to low productivity and conversely bigger screens to more productivity -> Productivity and Screen Size.

What can be worrisome are new interfaces that promise the same productivity gain as bigger screens but aren't screens at all. Think in this case of interfaces that uses your brain, haptic (pressure) feedback and other inputs that puts less strain on your visual cortex thereby relieving you of the need to focus with your eyes. Nevertheless, websites have the property that they are text and image based products and so unless this property changes, it will be difficult to come up with new technology that replaces reading and seeing images for users, something that we do so naturally. If man succeeds in changing this and adopting new ways to interface with tech that is more effective than reading, then still there is the option of changing the ad-based business model.

In any case, to earn the last 1 cent, I think the fact that everything is going mobile is positive. It will change the way we design websites, not only adapting them to cope better with different devices and screens, but also into making them more effective at providing us information because of the increasing pressure of a generation of users that are more impatient than the previous generation, and this is partly due to the fast on/off information access that we get from using mobile devices. In addition, it will challenge the current ad-based business model that came from (at least I think it did) from traditional print-based media.

Two cents added into the blog communal pot.

Comments

Popular posts from this blog

But Google what about mobile phones that do not support Javascript?

In the global device market, there are still between 0.2% and 5.4% of phones that do not support Javascript, at least in these set of countries according to this site. In case your mobile website falls within this set than what do you do when you want to optimize CSS delivery by deferring the loading of some CSS but still serving the complete CSS to non-Javascript websites?

Algorithm to sort edge list of simple polygon for 2D and 3D

Sometimes it is handy to sort an edge list. In this case I needed an algorithm to test for concavity of a simple 3D polygon with just one face. You can also apply the procedure on 2D because it just sorts an edge list that could contain either 2D or 3D vertices. The polygons were made in Blender v.2.67 , so the script had to be written in Python and executed via the Run Script button in the text editor. I didn't want to use fancy algorithms to sort edges because we're dealing with simple polygons, so I ended up writing my own. As a side note, the edge-angle checkbox in Blender, which can be used to see if a polygon is convex or concave didn't work for me, so I had no other choice but to first sort edges before I can apply angle calculations on consecutive vertices. Suggestions for improvements are welcome and hopefully it helps someone else who had to deal with the same (or similar) issues in Blender!

A scalable geometrical model for muscle and tendon units: An algorithmic solution on how to fit a template muscle on a high resolution muscle mesh

The reason for this blog post is to share a bit on a particular hard problem that I've encountered during my Master's thesis with a broader audience. I will try my best to write it in plain English, but as the problem is complex expect this to be a lengthy post with domain specific terminology.