We seldom propose ready-built solutions, but rather make sure to tailor our choice of technology to our clients’ needs in order to find the best solution. Whether you need help with a new idea, need assistance with an existing solution, or with optimization of your code base, we’ll be able to help.
The key to successful digital efforts is understanding how they enable your underlying business objectives. We help connect your digital investments to your business goals and advise on digital strategy.
Rhyme creates quality frontend structure that is scalable and maintainable. Attention to design and how things look and feel is in our DNA and something we pride ourselves with. Read more
We help you make the right technical choice to support your business goals. We are the partner that can build technically challenging solutions, while making sure that your product is modern, scalable and reliable. At Rhyme we like to say that we are “tech agnostic”, meaning we are never to be constrained in our choice of solution based on what we have done before. The rapid change and progress within frontend development means that we need to be free to constantly update our choice of tech in order to provide the best possible solution for our clients, instead of being burdened by how it has been done previously.
We provide more than just hands to write code; we provide leadership in terms of a counterpart that challenges the solution and how it helps you realize your strategy. Our goal is not simply to deliver on a proposed solution, we empower our teams to improve it, all the while enacting best practices of maintainability and sustainability to create a strong end product.
We integrate and work tightly together with design teams and stakeholders ranging from small to larger teams. We aim to effectively deliver actionable frontends that can be part of a single effort high fidelity delivery where the result can be part of a complete solution without change for years to come. Or more often and with more joy work together with cross functional teams to iterate well received user interface code going from first prototype to the MVP. And finally continuously improve on a production ready product to fine tune after well tested versions to amplify user experience, result and happiness. For example we delivered from a ready made design to ATG the well received voting page for their yearly awardÅrets häst.
On the other hand we were part of the larger product team in delivering Prism CNC (kan länka till våran interna case study också) to Sandvik AB. Where we started with a prototype and worked our way over the course of over a year to a production ready product and passing many milestones on the wayPrism.
Raising performance of existing applications by review and rationalization of code base, coupled with an overhaul of systems architecture and design. Read more
Improving and simplifying a current code base or architecture can sometimes be the most efficient way of increasing the performance of an application. Our goal is to improve application metrics with system-wide optimization, assessment of architecture and code inspection.
Our senior developers analyze the current solution by reviewing the code base and making an assessment of what can be approved and how, based on business goals and end-user experience, with the minimum amount of disturbance to uptime and performance. Opportunities include code deduplication, rationalizations of systems design and better measuring of performance. We generally seek to maintain what we can, while also laying the groundwork for further development of the current application.
To assess browser performance we use the browser’s developer tools.
Tandlakare.se, a product that has been through many years and many different developers and development cycles since it first was released. The lack of a cohesive vision of the code base and product was apparent. Many of the tools that we usually use today and take for granted were missing. We have added linting and have converted the code base to a consistent code style. While building new features we continuously build out tests for the legacy code base to try to ensure high uptime and a minimal amount of regression.tandlakare.se.
Backend development and infrastructure, including databases, APIs, integrations and cloud deployment to ensure scalable and robust performance of services. Our first choice is usually Node.js, which outperforms alternatives for many of our clients’ needs in terms of scalability and reduced complexity. Read more
We provide our clients with a full solution in terms of end-to-end development. That implies that we create applications that are well-designed, reliable, high-performing and flexible. At Rhyme we have deep expertise in setting up a scalable infrastructure, working with third-party integrations and systems design that enables your business goals by using the latest techniques available.
We use our thorough expertise in architecture, database design, APIs and integrations to build state of the art platforms. We choose the cloud infrastructure and tools that best allows our clients to deliver value to their customers.
The application we delivered for Navigios internal management tool is built on AWS for flexibility, cost & maintainability. It consists of two servers setup with: An Node.js/ Express backend exposing an API that delivers all needed functionality for a completely custom made internal tool complete with: document handling, questionnaires, user handling, two factor authentication, mailing services and more. It is delivered as previously mentioned node, MongoDB, nginx and various services on the AWS cloud platform.Navigio website.
We have gathered our greatest tips and tricks of what should be included in a digital brief. Clear communication and formulating clear goals is essential for a successful partnership. Collecting your views in a digital brief regarding what you want and what you’re after, as well as your requirements and restrictions, is a cornerstone to start that relationship. Read more
As the responsible for the product you probably already have ideas or input from colleagues and customers. Should you just make a list of comments, ideas of features, inspirational solutions, requirements and customer concerns and bring to the first meeting? Yes sure, why not - that’s a good start! We will not be content with a to-do list either, we will want to ask questions, twist and turn every part to challenge preconceptions - which is why it is good to have had the chance to think things through in advance.
The brief is a simple tool to collect and structure thoughts and ideas for our collaboration. It is a description of what you want us to do and help you achieve. It should answer the questions:
Background: who you are
Purpose: why you want to do this
Objectives: what you want to achieve
Target audience, other stakeholders and their needs
Prerequisites and constraints
We provide a template for you to fill out to address these questions. You might have subjects which do not easily fit into any of these categories - then note down anyway - the brief is meant to be a support and not something that constrains our discussion.
The purpose of the brief is to collect all the thoughts, requirements and constraints you can think of. Otherwise we risk missing important concerns because they are left out of the conversation. If something (e.g. a feature) is left out of the project it should be because of a conscious choice and not carelessness. Our team also needs the brief for the ongoing project in order to be able to make independent decisions. Throughout a project a thousand small decisions are made; everything from the choice of technical platform to the color of a button. With a brief in hand the objective, target audience and what problem we are solving is clear. Our team has a better chance of taking the right decision, without having to bother you with every detail and you can concentrate on giving input during the bi-weekly sprint meetings.
It can be daunting and time consuming to get formulate exactly what you want. How to prioritize? Is this really important? Can we change our mind? Is this really the actual objective or is it actually something else? Should I put down my needs or the end-user? Both?
If you’re struggling, jot down what you can and move on. Not knowing is also an insight. Better to make that clear than guessing. Part of our job and why we want to have this conversation is to figure this out. So, if there are things in the brief template that you cannot answer, write it down and we’ll discuss it and how to handle it.