Documenting code, one commit at a time.
Recently, our team working on the Ryuu-no-Mi/Inmotech-Backend project addressed a critical security and usability issue related to Cross-Origin Resource Sharing (CORS) in our OAuth 2.0 implementation. This fix was crucial for ensuring seamless and secure interactions between our decoupled frontend applications and the authentication server, preventing common browser-based security blocks.
The Inmotech Frontend project recently implemented a new feature to enable seamless online payments using Stripe. This enhancement allows users to subscribe to premium plans directly within the application, offering a smooth and secure checkout experience. This post details the frontend integration steps, from setting up the necessary libraries to creating the user flow for successful and
In the Inmotech-Frontend project, which facilitates the management and creation of property listings, a recent update focused on enhancing data integrity and user experience during property submission. This change was primarily driven by new backend requirements that mandate specific fields for all new properties.
Previously, the
In property management applications, displaying accurate and comprehensive property details is paramount. Small inaccuracies or missing information can significantly impact user experience and the overall reliability of the platform. The continuous evolution of data requirements and the pursuit of pixel-perfect precision are ongoing challenges in frontend development.
Ever spent hours debugging a mysterious bug, only to find it was a simple mismatch in field names between your frontend and backend? It's a common pitfall, especially in rapidly evolving applications.
In the Inmotech-Frontend project, our team recently tackled precisely this challenge to streamline property management features.
We encountered an
In the Ryuu-no-Mi/Inmotech-Backend project, we continuously strive to improve the user experience, particularly in property search and filtering. A key aspect of this is how we present geographical data to users, allowing them to quickly narrow down their search by location.
Previously, our property
Our ongoing work on the Inmotech-Backend project, a core component of Ryuu-no-Mi's property platform, recently focused on significantly improving its property search capabilities. With a catalog exceeding 30,000 properties, the challenge was to offer highly accurate geographical filtering and a responsive user experience through dynamic search facets.
Previously, our search
On the Inmotech Frontend project, we recently tackled a common challenge in API communication: inconsistent URL query parameter serialization. This often arises when integrating with backend services that expect a specific format for array parameters, differing from the default behavior of popular HTTP clients like Axios.
Ever found yourself debugging an API request only to realize the backend
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.
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)
