On my last post I focused on issues that I’ve found a solution, this one is going to be about bugs and issues that I couldn’t find a solution and/or things that are impossible to do on the iPhone and iPad. It is important to note that I didn’t spent too much time searching or trying to find solutions for each problem but I consider most of them to be impossible to solve without a new OS release…
Read more…
I’ve been delaying this post since I wrote a rant about the iPad. The delay is mainly because I never found time to create sample files or record screencasts showing the bugs so I decided to publish it without any working examples since I don’t think I will have enough time or patience to isolate the problems and document it anytime soon, so you will have to believe that what I’m saying “is true” and that the bugs exist… Think of it as a reference in case you have any of those issues and not as a definitive way of making those things work, some bugs are only present on older versions of iOS and may not be easy to replicate. I’m sure I will leave a lot of important stuff behind but at least I’ll try to cover some bugs and how I solved them. I will try to be brief.
Read more…
Imagine you are working on a project targeted for the iPad, Chrome and Safari that should contain an interactive HTML5 video… Design and feature-wise the project seems pretty simple and since you assume that the newest Webkit browsers have a good support for CSS3/HTML5/JavaScript (and Steve Jobs says it’s “amazing”) you shouldn’t have any issues building it, especially since you have coded many video players and interactive videos using Flash before and you are pretty experienced with HTML/JS projects and have used HTML5 video and CSS transitions/animations on a couple other projects.. A couple weeks of development should be fine… – Now you have a big problem.
Read more…
A couple weeks ago I wrote a post about why the HTML5/JS community should respect the Flash community and it got way more attention than I expected, now I’m a little upset that I forgot to say some really important things and also because the way I wrote made some people think that Flash developers are “better” than other developers and that HTML5 is almost the same thing as Flash (both things aren’t true)…
I stated that Flash developers are used to solve problems that the JS community is only starting to have, but I didn’t mentioned that the JS community is also solving issues that Flash developers never had to handle. Even though they share a few things, each technology requires a complete different set of knowledge and experience, that’s why companies usually hire different people for each position… - that’s another reason why the communities should respect each other.
Read more…
Nowadays the debate about HTML5 vs. Flash became really popular and a lot of misinformation is going on… My intention with this post is NOT to say that one technology is better than another, specially since I don’t believe that one is better than another but that they have different purposes, my idea is to show that there is a bunch of things that those communities can learn from each other… Please read the whole post before commenting. My intention is not to start a flame-war. – I’m an HTML/JS/CSS developer that happens to know Flash/AS3 too, not the opposite…
I think one of the main reasons why the HTML community is biased towards Flash – besides the annoying banners and “skip intro” websites – is that flash is a “closed box”, they don’t know how it works, don’t know what is inside, the source code doesn’t show up when you view the page source, a lot of people use the technology without a good reason, don’t know the pros and cons, don’t know available features, isn’t “standard”, etc… (people tend to fear/dislike what they don’t understand). Mac users also complain about the performance of full-screen video (which was improved a lot with Flash Player 10.1). I’m going to try to explain very briefly the Flash platform and to show some similarities but without getting into details about each feature (for brevity).
Read more…