Web development

About Tinloof

We're a team of senior web developers and designers that are passionate about the work we deliver.

We operate fully remotely and work with companies all over the world.

When we say we become part of your team, we really mean it

We operate best when we are embedded within your organization as regular team members.

Our web development process is transparent, since we're fully remote, we believe written and shared communication is key to our success.

We share our progress regularly, discuss ideas with you in real-time on Slack or Discord, and our contributions to your codebase are accessible and easy to review.

We're fans of Notion, so when we have the possibility to use it, we set up from day 1 a roadmap and a board with our day-to-day tasks.

We write code for humans, not just for browsers

We believe that web development is about writing code that both browsers and humans can easily understand.

We write code that other web developers will review or add features on top of, so simplicity and documentation are part of our web development cycle from the first line of code that is shipped.

We're research-oriented

We're lucky that web development is a field full of day-to-day innovation.

Every day there are new ways to solve web-related problems, so we conduct research to find the best tool or method to implement various features.

We conduct research in between projects and write articles about findings. You can check all our articles on our blog page.

We don't reinvent the wheel

We have an internal code generator and various libraries that help us avoid rewriting the same code over and over again.

We also research often external tools and libraries that solve specific problems, and when validated, we rely on these tools instead of writing custom code.

To understand the benefits of this, let's take authentication as an example.

If we write code from scratch to log in and register users, we'd have to account for time to implement the feature, test it, and document it for other developers to make adjustments to it in the future.

Instead of doing that, we rely on platforms such as Supabase to have authentication in place from day 1. Because we use a platform such as Supabase, a huge part of authentication is already tested and carefully documented with examples.