Your current filters are…
by Todd Sawicki
Werewolf, a variation of the Mafia game, is spreading like wildfire in the tech social circles. We've hosted overnight games in secret in the past at SXSW, but this time, we want to get more people involved. The game is the great equalizer. Though deceit, honesty, and raw powers of reasoning, you can get to know amazing people and build great friendships. This panel with long-time Werewolf players will teach you the basic rules, the best practices (yes, there are best practices even for a game), and how to host the game yourself. Come to SXSWi and leave with an amazing tool to build great experiences forever. Trust me, I'm a villager.
by Charles Ying
Learn different ways to integrate HTML5 into native apps, what tools you can use, and when to build your own. We'll cover achieving high graphics frame rates, touch responsiveness while conserving battery life. Learn the benefits and tradeoffs of mobile graphics hardware acceleration in animation and emulating native UI in mobile web browsers. We'll also touch on Flipboard's use of HTML5.We'll cover these specific technology areas: WebKit and JavaScriptCore; native view system architecture, animated scene graphs; and hardware accelerated graphics drawing and compositing.
by Andy Hume
In the early days of CSS the web industry cut its teeth on blogs and small personal sites. Much of the methodology still considered best-practise today originated from the experiences of developers working alone, often on a single small style sheet, with few of the constraints that come from working with large distributed teams on large continually changing web projects.
The mechanics of CSS are relatively simple. But creating large maintainable systems with it is still an unsolved problem. For larger sites, CSS is a difficult and complex component of the codebase to manage and maintain. It's difficult to document patterns, and it's difficult for developers unfamiliar with the code to contribute safely.
How can we do better? What are the CSS best practises that are letting us down and that we must shake off? How can we take a more precise, structured, engineering-driven approach to writing CSS to keep it bug-free, performant, and most importantly, maintainable?