# Technical diagnostic of +DERA for MaderaPlus | abuenoben

> Technical diagnostic of +DERA for MaderaPlus: reproducible staging, 203 documented API calls and 23 prioritized actions to guide product evolution.

Canonical URL: https://abuenoben.com/en/cases/maderaplus-technical-diagnostic
Language: en

[Back to case studies](/en/cases)

B2B forestry technology, offline Android app and legacy back office

Diagnostic staging in place, 203 backend/API calls documented, 32 anonymized business requests, 115 issues/improvements reviewed and 23 prioritized actionable entries.

By [Armando Bueno Ben](/en/about)

![MaderaPlus logo.](/images/cases/maderaplus-logo.png)

## How it was delivered

01

### Starting point

MaderaPlus needed to understand the real state of +DERA: field Android app, offline synchronization, backend/API, legacy website and release process before investing in evolutives.

02

### Intervention

I rebuilt the technical map, set up local staging, tested the app, backend and web with anonymized data, reviewed the historical issue log and turned the findings into a 30/60/90 roadmap.

03

### Ownership taken

Senior technical diagnostic, staging QA, evolution architecture and backlog prioritization.

04

### Outcome

Diagnostic staging in place, 203 backend/API calls documented, 32 anonymized business requests, 115 issues/improvements reviewed and 23 prioritized actionable entries.

## How this applies to your agency

Executable technical audit, reproducible staging, app/backend/web testing, issue prioritization and roadmap to sell or decide the next phase with less uncertainty.

## Project context

[Open public website](https://www.maderaplus.es/)

Context

B2B forestry technology with field app, web back office, API and offline/online synchronization.

Frame

Direct client with permission to show brand, logo and public website.

Role

Technical diagnostic, staging, QA, prioritization and roadmap.

Visibility

Public case with brand and website; no internal screenshots or private +DERA materials.

## Technology and decisions

Technical base

Android Java, SQLite and offline sync, CakePHP/JSON API, Joomla/PHP legacy, MySQL, Docker Compose, staging fixtures and Kotlin/KMP, Compose, Ktor and React recommendations.

Time frame

Scoped diagnostic with documentation delivery and review session.

What I learned

Before selling evolutives on a live legacy product, uncertainty should become evidence: environment, tests, releases and agreed priorities.

## Related services

[Android maintenance and evolutives](/en/android-app-maintenance)[Backend, API and integrations](/en/services/backend-integrations)

## Do you have a delivery with a similar risk?

With the objective, timing, current state and validation owner I can tell you whether there is a real fit and what I would review first.

[Tell me about your project](/en/contact?organizationType=agency#contact-form-shell)