In the Ryuu-no-Mi Inmotech-Backend project, our goal is to provide a robust platform for property management. A critical component of any such platform is an intuitive and powerful search capability that allows users to find properties based on highly specific criteria.

The Problem

Traditional basic search often falls short when users need to refine their results based on multiple criteria,

Searching for properties can often be a frustrating experience. Stiff search interfaces that don't dynamically adapt to your choices or provide relevant groupings can quickly turn a hopeful search into a chore. In the Ryuu-no-Mi/Inmotech-Backend project, we've recently rolled out a significant feature to transform this experience, particularly for 'venta' (sale) and 'alquiler' (rental)

Introduction

Ever run into a seemingly simple database operation, like lowercasing a text field, only for it to throw a wrench in your application? This is a common pitfall when dealing with large text data types like CLOB (Character Large Object) in databases, especially within Java applications.

Imagine deploying a new environment or resetting development data, only to find critical fields consistently null or empty where they shouldn't be. This seemingly minor oversight can lead to cascading issues, from UI errors to incorrect business logic. Such was the challenge we recently addressed in our Ryuu-no-Mi/Inmotech-Backend project.

Our Ryuu-no-Mi/Inmotech-Backend handles a variety

Introduction

Modern applications thrive on granular control, especially when it comes to searching and filtering data. For users interacting with platforms that manage diverse information, the ability to pinpoint specific items based on their attributes is crucial. This post delves into a recent enhancement made to our backend application, focusing on improving its search capabilities by

Introduction

Working with stale or insufficient test data can significantly hinder development and compromise the reliability of testing. Developers often find themselves wrestling with limited datasets that don't reflect real-world scenarios, leading to missed edge cases and a less robust application.

At Ryuu-no-Mi's Inmotech-Backend project, we faced similar challenges.

Imagine a gym membership system where every family member needs their own access, but the family's main plan dictates how many members can join and when their access expires. This challenge is similar to what we tackled in Inmotech-Backend, enhancing our subscription management to support more flexible agency and agent-level plans.

The Challenge: From Static to Dynamic

Previously, our

In the fast-paced world of web applications, friction in user authentication can be a deal-breaker. A complex signup process often translates directly into lost users. This is why simplifying access, like integrating social logins, becomes a critical enhancement. Our Inmotech-Frontend project recently embraced this philosophy by integrating Google OAuth2, offering users a quick and secure way

Introduction

Integrating third-party services, especially critical ones like payment gateways, requires meticulous attention to detail, particularly in error handling. A small oversight in configuration can lead to significant headaches down the line. In our Ryuu-no-Mi/Inmotech-Backend project, which orchestrates various backend functionalities including payment processing via Stripe, we

In the Inmotech-Frontend- project, like many modern applications, we rely on environment variables to manage configurations and sensitive data. These variables might include API keys, third-party service credentials, or specific settings for different deployment environments. While incredibly useful for flexibility, managing these variables comes with a critical responsibility: ensuring they