ProjectsFor those of you who need to know, or are mildy curious, we offer the following examples of our “success stories” – our earned STARs. Because we often work “behind the scenes”, in some cases, some of the following stories will not disclose the name of the company with whom we were engaged, the name of the project, or any other identifying information. Ready to work with us, fill out out the following form. |
| Client: Confidential Product: Confidential Year: 2010
Situation: Our client provided a tool with which their customers could build and/or customize a website. This editing tool ran on the Windows desktop. Our client desired to move their customers to a web-based editing tool. Task: We were engaged to replicate (and extend) the functionality of the desktop editing tool in a new web-based experience. Action: This application makes extensive use of client-side (browser-based) technologies, including: JavaScript, jQuery, CSS, caching, ajax Web development was done in a modern Java stack. Result: Our client successfully deployed the web tool to their clients in phases over a one year period of time. The first live release occurred five months after we began production- allowing our client to sign up Mac-based customers for the first time. The full release occurred nine months after we began production. The product continues to be used and extended today. |
|
Client: Confidential Product: Confidential Year: 2011
Situation: Our client wanted to provide their customers with an electronic payment system that allowed users to send and receive payments. Task: We were engaged to develop this payment system. Action: This system was implemented on Grails. The front end uses jQuery, CSS, and GSPs. On the back end we used MySQL for the database and JBoss for the production server. Result: Payments can now be made directly to a bank account (ACH), as well as through credit cards. We also initiated unit and integration test strategy to increase reliability of the code base. |
|
Client: Confidential Product: Confidential Year: 2011
Situation: Our client was running a promotional program on their website. Task: We were engaged to create a Facebook application and integrate it with the website. Action: We were able to create the application so that users could participate in the program on Facebook without having to leave the website. We also were able to make sure that every time someone participated it showed up in their Facebook news feed. Result: The program is still being used today and has had overwhelming success with more than 34,000 likes. |
|
Client: Confidential Product: Confidential Year: 2011
Situation: Client’s code base was using old technology and an update was needed in order to deploy the application in the new data center. Task: We were engaged to migrate the code to the latest version of Spring. Action: We used Spring 3.2 for the framework, JBoss 5.0 for the server, and JUnit 4.x as our unit testing framework. Result: The changes have made the code easier to update and the automated test coverage is now 80%. |
|
Client: Confidential Product: Confidential Year: 2011
Situation: Our client approached us with a performance problem with their mobile application. A task in the application took over a minute to complete on older mobile devices rendering the application unusable. Task: We needed to find out what was causing the application to slow down and then make changes to the application so that it would perform faster. Action: We used ANTS Performance Profiler to find which areas of the offending code were the slowest. Then created a tool that could ensure that changes that were made were still producing identical output to the old code when run with a few different parameters. We made changes to correct the use of a hash table and replace very slow indexing into an XML document with some minor caching that only needed to parse the XML document once. Result: The speed of the offending code was improved by 32 times. This reduced task completion time from over a minute down to a couple of seconds on older mobile devices and improved the desktop version of the code from six seconds down to sub second speeds. |