Three months ago, I wrote an article titled “Remote as default, office as an option. Our remote work approach”. On it, we’ve tried to share our vision on the future of work.
Design handoff is the moment where all the little pixels are shared with the Engineering team to make them come alive. This is an ongoing process that should be respected as much as the final result. We use Zeplin to help us with this.
One of the main goals of a developer is to automate every operation that turns out to be repetitive. This gives them to focus on the actual problems of the project and lets them develop faster with fewer worries.
Every dynamic website consists of two main parts: the backend and the frontend. The backend, which in marketing websites is commonly a Content Management System (CMS), allows the website owners to manage as much content as needed without handling code changes. The frontend displays all of that content for the website users.
There is no denying it, hybrid mobile development is booming and becoming the main option when considering developing a mobile application due to the lower costs and faster development time. But what are the implications of going for a hybrid approach instead of a native one? What are the advantages and disadvantages of choosing one of the approaches?
Whether you are starting your business, or expanding your team, it is essential to make decisions to build the product within the budget and quickly as possible without compromising quality. To do so, you can create or expand the team internally, hire an external company as a partner, or even choose a hybrid approach. In this article, I will outline the advantages and disadvantages of each method.
Remote vs Office is one of those never-ending discussions. One in which there are few right or wrong answers. Context matters, so the best approach for “you” always depends on it. This post solely intends to share our “story” and approach to this topic. In a few years, we’ll see if it’s the right call or not.