Managing service integration files is a fundamental part of maintaining project stability. Recently, we performed a routine update to the service configuration file within the Ryuu-no-Mi/RK-ACM-Inmobiliaria_FORK_ARTURO project to ensure continued communication with external service providers.

The Challenge of Static Configurations

Configuration files often serve as the bridge between your

Documentation as Architecture

In the development of Ryuu-no-Mi, we have focused on balancing rapid feature growth with long-term maintainability. While much of our effort recently has centered on refining the Repository Pattern to decouple our data access logic from the domain layer, we have also reached a milestone in internal knowledge sharing: updating our central project documentation.

Bridging the Frontend and Backend

When working on the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, the bridge between our Angular frontend and our Java backend relies on clear, robust communication via RESTful services. Connecting these two worlds is often where developers encounter the most friction, especially when dealing with data serialization and reactive streams.

In the Inmotech Frontend project, enhancing user experience often involves making data easily discoverable. A recent feature focused on implementing robust search and filtering capabilities, addressing the common challenge of navigating large datasets efficiently within a web application.

Imagine sifting through a library where all books are simply piled together.

Integrating third-party authentication can be a developer's double-edged sword: powerful features, but often with inconsistent data guarantees. In our Inmotech-Frontend project, we recently encountered a classic example of this when dealing with OAuth user data – specifically, how null date values can unexpectedly break a smooth user experience.

Our Inmotech-Frontend application leverages

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.

The Challenge: Backend Requirements Meet Frontend Forms

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.

Project Context:

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.

The Problem: Mismatched Data Contracts

We encountered an