The Full Stack Podcast – Episode 01

TFS – Episode 01

It’s here! Our first podcast, grab it now direct from this link: The Full Stack Podcast – Episode 01

Show Contents:

  • Introduction of Casey and Phil
  • Chrome Mobile Developer Tools
  • RWD make-over of shop.ifit.com
  • A charity website build (turns out there wasn’t really any ranting 😉 )

Show Notes:

Phil Dutson is the author and/or co-author of “Sam’s Teach Yourself jQuery Mobile in 24 Hours”, “jQuery, jQuery UI, and jQuery Mobile: recipes and examples”, “The Android Developer’s Cookbook 2nd Edition”, along with the video series LiveLessons: jQuery Fundamentals”. He works for ICON Health & Fitness as the mobile, ux, and lead eCommerce developer working with IBM Websphere Commerce.

Casey Doolittle is a Technical Editor and lead Java developer for ICON Health & Fitness. Specializing in all things back-end, he brings programmer charm to the fore-front with a wealth of knowledge and hard-earned expertise while also grappling with new technologies, frameworks, and languages including MongoDB, Node.js, Ruby, SpringMVC, and more.

Chrome has released a new beta version of the browser for Android that can be found at the Google Play Store. After downloading and installing that, you can set up remote debugging (by following these instructions) and now you can see your device screen as well as manipulate it. If you have Chrome Canary (get the canary channel here) then you also get some great new features! See the official write up and screencast by the man Paul Irish himself for the demo of the tools on HTML5Rocks.com.

Feel free to visit shop.ifit.com and let us know what you think of the RWD change. This was an extremely fast build (total time was about 1.5 weeks), so there may be a few rough-edges, but overall we are very pleased with how the site turned out. Note that we plan to start using SPDY in the future (which is why the site is secure from end-to-end).

The charity that ICON supports is called the ICON Foundation. This charity is dedicated to helping children, families, and employees in any way they can (they’ve donated shoes, food, and more to the local community). Every year they hold a two day sale to help raise funds. You can learn about the ICON Foundation by visiting the website. This year we set the site up on a new framework and added a open-and-close feature that matched when the brick-and-mortar store was open. The front-end layout was based on an old version of what we call “base”. This framework is what our front-end and back-end teams start with when creating any new web projects. You can check base out by visiting the project page on GitHub.

Sponsors for this episode were NordicTrack and ProForm, thanks guys!

 

As will be the norm, feel free to drop any questions, comments, or concerns in the comments section of this page.

Find us on G+, we are +DevcannonTFS

We are working on iTunes syndication and will post as soon as possible!

3 thoughts on “The Full Stack Podcast – Episode 01

  1. I love the speed and responsiveness of shop.ifit.com. But yeah I was going to ask if you used angular or some other JS MV framework, but then you guys said you didn’t. 🙂 Did you find those frameworks to just be too much overheard for what you were doing?

    BTW you guys rock. Love the podcast.

    • Thanks for the response, questions, and comment Brett!

      To answer, we were playing with ember (and loving handlebars), and then checked out Angular (which is also pretty epic). But when it came down to implementation with our custom CMS (because we built one using MongoDB), it was easier (and lighter) to include handlebars for some light template work and then lean on SpringMVC for handling our urls.

      The con to that method is that you get “page-glitch”, you know that second of white everytime you move from one page to another. So to ease the pain we focused on keeping the pages as light as possible and doing as much with CSS as we could.

  2. Thanks for the info! Screencast your device screen to desktop is awesome!! This might be the thing that pushes me off developing in FF and over to Chrome!!

Comments are closed.