We are a Westshore-based group of talented designers and developers devoid of heavy corporate structures, approval processes and tight boundaries. Noted by our clients as giving that “little extra”, we seek to ship customized solutions, build sustained client relationships and deliver strategic counsel with zealous service.
Looking for a no-politics zone to do your best work? Mercury is the place for you.
If there is one platform we are most rooted in, it’s the web – modern responsive techniques are our stock in trade. If you know these technologies, you can make it anywhere.
HTML5It all starts with clean, semantic, standards-based markup. Local storage, geolocation and native media players are some of our favorites.
CSS3
Separating content from presentation with judicious use of SASS use (mixins, partials and variables) keeps our UIs robust. And BEM’s not so bad, either.
JavaScript
Bundlers and transpilers like WebPack and Babel support our use of the latest JavaScript and versions of React, Angular and Knockout libraries.
Robust data layers go a far way in these parts – without them we just have websites, not web applications.
SQL ServerSQL Server, whether on prem, installed on IaaS VMs or consumed via SQL Azure provides the hearty data storehouse we need for scalability and rapid querying.
MySQLIt’s not all about SQL Server if you want to get relational with it – MySQL definitely show up around the Mercury shop, too.
MongoWe have much love for Structured Query Language but NoSQL is cool, too. And there’s nothing like Mongo for a document database, if you ask us.
Application code, service layers and even middleware are big parts of what we do around here. We like to keep the business logic clean and separated and our services RESTful.
.NET and C#C# and the .NET Framework are old friends of ours – while not as trendy as the JavaScript frameworks it’s hard to do better when you need to roll business logic, marshal data or automated processes.
MVCWebForms and ViewState are history – you won’t find them around here. But if you want to roll with .NET then MVC is your friend – and it’s good for JavaScript development, too.
WebAPIYa, we went the WCF route. Then we simplified with WebAPI and never turned back.
NodeLow overhead and thin requirements – there’s a lot to like about Node. And there’s nothing like being able to share JavaScript between the data, application and interface tiers.
We love the web. Like, really love the web. But sometimes you have to code to the platform to really get the most out of it. Here’s how we do it.
React JSReact Native extends that elegance of React development for cross-platform native development. Share common code with your web application and nearly 100% across iOS and Android with React Native.
XcodeWe love the web and we love React Native but sometimes you need to get straight down in Xcode to Objective C and Swift for your app or custom React Native components.
Android StudioMarket domination isn’t easy but Android does it well. We rock Java in Android Studio to build out custom native Android apps and React Native components even more often than iOS.
Words about what we use systemically.
GitDistributed version control for the win.
Continuous Delivery / DevOpsBuild, integrate and push to testing, staging and production environments on every code commit.
Azure / Amazon Web ServicesDeploy to the cloud.
SeleniumTest every key function of the application on every release so you know you’re not pushing out regressions.
WebJobs and Function Apps are both services in Azure to run triggered or scheduled tasks. This blog posts compares the two services and outlines cases where one solution may be preferred over the other.
SharePoint is an industry standard platform for creating a company intranet, but the out of the box styling leaves something to be desired. Even a well-designed site can fail to engage employees if it isn’t visually appealing. In this blog, I will explore several options SharePoint offers to customize the user experience, and explain the pros and cons of each approach.
2016 was a year of great success and growth. We experienced technical evolution and shipped a large volume of client solutions. As 2017 approached my team got together to establish our technical vision for the upcoming year. We decided that this is the year for us to mature how we build applications, ratchet up our focus on quality and become more masterful with our new skills. In this blog series I will share our vision and objectives for the coming year and welcome your thoughts on where your firm is focused in 2017.
Learn about creating, employing, or utilizing a framework for your functional tests to drastically improve your testing that benefits of creating functional test framework and what that framework might look like.
As a relatively new architect-level hire at Mercury, I have spent a large amount of time exploring code bases that are new to me. In that exploration, I have come across a variety of source code peculiarities and problems related to issues with naming conventions. These are fairly rare situations and as such can take a while to diagnose and get to the true root problem. The issues I will describe below are specific to situations in Mercury’s development process, but might help to identify possible pitfalls in yours.
Design is incredibly subjective and each person has their own opinions and interpretations. To ensure your vision is realized you can implement interface prototyping to visually display thousands of words worth of design and development requirements regarding how a system should both look and behave.
Start progressing your career now by joining a talented group of professionals who craft and ship incredible web and native applications.
View Open Positions
