Javier Martínez López
Technical profile
I develop software with .NET and Blazor, connecting interface, backend, data, security and deployment through one product-focused view.
01
Professional evolution
I have built web solutions since around 2018. My earlier work included more WordPress and traditional web development. Today my work centers much more on C#, Blazor Server and WebAssembly, PWAs, Blazor MAUI, ASP.NET Core, APIs and data. WordPress and WooCommerce remain useful, complementary skills.
02
Application types
- Blazor web applications
- Installable and offline PWAs
- Windows solutions with Blazor MAUI
- REST APIs and integrations
- SaaS and multi-tenant software
- Processing, synchronization and documents
03
Architecture approach
I start with the problem, data and responsibility boundaries. I prefer compact structures that separate real responsibilities, keep authorization close to the domain and can evolve without empty layers.
Stack
Technology grouped by responsibility
Applications
- C#
- .NET
- Blazor Server
- Blazor WebAssembly
- PWAs
- Blazor MAUI
Backend
- ASP.NET Core
- REST APIs
- SignalR
- WebSockets
- Integrations
- Automation
Data and access
- SQL Server
- Entity Framework Core
- IndexedDB
- Identity
- JWT
- Roles and permissions
Web
- HTML5
- CSS
- JavaScript
- Responsive
- Accessibility
- Technical SEO
04
Private solutions
Private business experience is summarized by capability: web and Windows applications, PWAs, ASP.NET Core, SQL Server, Identity, JWT, roles, permissions, validation, imports, exports, automation, documents and technical error handling. Names, industries, clients, modules, URLs and identifying screenshots are not published.
05
Working approach
I develop and collaborate remotely on projects from analysis and architecture through deployment and evolution. I document decisions, test according to risk and preserve a rollback route for operational changes.
This page has clean browser print styles.
Shall we discuss the solution you need to build?
Share the context, constraints and current state. The conversation starts with the problem, not a predetermined technology.