“Eating” Spaghetti Code for Breakfast, and “Serving” Custom API Framework for Lunch

Or How to Setup an API Framework for a Client that Serves a Million Users Monthly Without Disturbing Them

Our client serves a million customers monthly. Over the years they have worked with multiple vendors who have built apps on top of the legacy code system, which overtime has made it extremely complex and unstable. All the services in the client’s portfolio were developed by different vendors/teams who had various architectures and patterns. Every service had it’s own login and monitoring, plus they all were mutually dependant.

Continue reading ““Eating” Spaghetti Code for Breakfast, and “Serving” Custom API Framework for Lunch”

DevOps @ Vicert – Lessons Learned

Through many years spent developing various applications, using various technologies and working with different clients, we have tried a number of diverse development methodologies and techniques, in search of the most optimal development process. But first, we had to define what optimal means for us.

Some would argue that the optimal process is the one that produces the required output (working functionality) the fastest. While that might be the case for small, simple projects, we find that on a large enterprise scale, the fastest output does not usually produce an optimal result.

Continue reading “DevOps @ Vicert – Lessons Learned”

How to integrate multiple Wellness devices using Human API

In a recent project for one of our clients, we came across a need to gather data from multiple wellness devices. We were faced with a choice between creating a custom connector for each device’s API, or using a service that gathers data in one place.

One possible solution was Human API (http://www.humanapi.co/) who stated that they provide an easy way to get data from multiple health systems and wearable devices (like Fitbit, Misfit etc.). Another one we found interesting (especially for enterprise solutions) would be Validic (https://validic.com/). We will not refer to it in this article, but it may be a focus of a separate article in the future.

Continue reading “How to integrate multiple Wellness devices using Human API”

User Driven Design: Three Steps to Breakthrough Digital Health Care Solutions

Kent Lawson is the Health Care Practice Lead at IA Collaborative, a preferred partner company.

Together with IA Collaborative we offer our clients in the digital health space a full service solution development process, from research, design and deployment of applications to consultancy and domain specific problem solving.

Throughout the year we will invite our trusted partners to guest blog to introduce new perspectives and angles on digital health.

The key to innovation—any innovation—is seizing latent opportunities and solving real problems for real users. At IA Collaborative, we call it user driven design.

User driven design includes three course of action and reaction, all focused on taking insight to action:

  1. Design Research- Researching real users and key stakeholders, in-context.

  2. The Journey- Understanding the current journey of any user or any product, the gaps that exist today, and most importantly the potential to fill or capitalize on those gaps.

  3. Design & Develop- Designing and developing the ideal future state, collaboratively with a multi-disciplinary team, including all key stakeholders.

ia-collaborative-home-1.jpg

Continue reading “User Driven Design: Three Steps to Breakthrough Digital Health Care Solutions”

Vicert @ “Berlin API DAYS 2014”

In May 2014, Berlin was the host of API Days convention, and this time it was pretty much developer oriented. Naturally, Vicert has sent one of its team members to attend. Here are the impressions.

Are Web APIs that big of a deal?

Yes, yes they are.

Web APIs are gaining in importance as a way of providing software, but also as an integral part of the web site. Developing and owning Web APIs can be very profitable (Google Maps comes to mind) so it is no surprise that there are more and more startups with Web API as their product.

Continue reading “Vicert @ “Berlin API DAYS 2014””

#2 Spring: Manipulating Salesforce objects

In Part 1 of this topic, we saw how to do OAuth authentication with Salesforce  using Spring. In this part, we’ll see how to fetch and update records  and upload documents to Salesforce using Force.com REST API.

Using Force.com REST API from Spring Web application – Part 2: Manipulating Salesforce objects

Force.com  REST API Resources are used to manipulate objects, execute queries,  display API information etc. Each resource is tied with a specific resource URI which is used to read, create or update record. All URIs  have common base URI: “http://domain/services/data”. Domain is usually instance URL retrieved during authentication, or a domain pointing to some Salesforce instance.

Continue reading “#2 Spring: Manipulating Salesforce objects”