In the summer of 2014, I was contracted and assigned to develop the mobile experience for Life Technologies.
Life Technologies Homepage in Mobile
Partnered with Moovweb
, we were able to generate mobile optimized workflows from high-traffic areas like Homepage, Cart/Checkout and PDP. Several mobile optimized workflows were developed fairly quickly and we successfully launched in all regions (English only) in January of this year.
Client and vendor teams were geographically split, yet worked in unison to accomplish this project at the expected go-live date. The desktop experience is transformed with Moovweb’s SDK and deployed to their cloud infrastructure. This allowed front-end development teams to start the project fairly quickly without too much reliance on back-end development support.
The next challenge relies heavily on building and maintaining the experience while integrating their tech stack w/in Thermo Fisher Scientific standards.
Visit m.lifetechnologies.com on iOS or Android mobile browser.
I’m a big fan of The Big Bang Theory and I couldn’t resist playing around with Sheldon’s friendship algorithm. It’s pretty much one object represented as
Sheldon guided by the module pattern (thanks to Addy Osmani).
I encourage you to fork this code and get some zen coding in. Since the logic is “safely” protected by
Sheldon, you should be able to integrate any boilerplate of your choice for some fun interfaces. Also, feel free to refactor the logic when needed. It could always be better. That said, kudos to Wolowitz for plotting out the loop counter and escape.
You can also view the demo here, here.
In the Fall of 2013, my team was tasked with R&D on integrating a search solution within the University of Rockies. Starting from the ground up, we pursued the idea of open-source search server, Apache Solr. After hours vetting out a workflow and experimenting, we were able to create a search product that not only touches base with Rockies, but can be extended to other web properties owned by the Marketing Group.
Some keypoints we put into consideration were the following:
- Search results….what type of results should we expose?
- Crawling and indexing…how do we crawl our domain and index our results?
- Web security…what standards do we need to put in place granted our search server is open-source?
- Third party dependencies…can we bring application ownership in-house?
- Future maintenance…what is our SOP and response time as the domain’s content changes?
- Technology Services protocols…what moving pieces are pertinent to change management guidelines, etc.?
The official release of UoR search went live in December 2013 and continuous improvements are slated throughout the year, so stay tuned. For now, feel free to explore this feature at, www.rockies.edu.