My favorite articles was Ethan Marcotte’s great introduction to the modern web browsing landscape and the choices we must make when adapting sites to desktops, tablets, and smartphones. I learned that from a developer’s perspective, the web is very transient and nothing remains permanent for long. I learned about the challenges of compressing photos and blocks of text into readable designs. While I sort of understood there was work being done to make this happen, I never really considered all the nitty-gritty details before.
I thought the next article was a tad confusing, but only because it was presented in a way I’m not really used to. I learned about the different components of screen adjustment (width, height, float, margins) and how they run the show. I was fascinated at learning there was a site called ProtoFluid where one can simulate the view of a phone from your computer. Talk about innovative.
The final article held my attention because I knew I had to make a judgement over which method was the best by the end. In my opinion, I prefer the responsive method, as this seems the easiest to develop and will heal the rift between phones, tablets, and PC’s. A native app option will work well for your most heavily-used sites, but it’s good to be able to explore the web independently on your phone.
I also thought the second article was confusing, but after rereading it a few times I understood it more. I also like the image you used to show the difference between the sizes. I personally like the native app but I do see your point about independently exploring the web.