# NIFYA main page redesign brief

- Original URL: https://nifya.com/
- Run date: 2026-05-19
- Status: mockup exploration only; no production code changed.

## Target audience and purpose

NIFYA needs to quickly explain a serious workflow: official/public source monitoring, relevance filtering against user intent, verified alerts, and agent-ready proposal workspaces. The homepage should make this feel trustworthy and immediately actionable for legal, grants, business, and public-sector users.

## Visual analysis of current page

- Desktop: the headline and benefit cards are clear, but the hero's large blank product frame weakens product credibility and creates visual dead space. The floating email capture card competes with the main CTA and partially covers downstream content.
- Desktop mid-scroll: the problem cards are understandable but feel disconnected from the hero; the email card remains fixed over important content.
- Mobile: the initial viewport is dominated by a blank product frame and floating email capture before the headline, so the value proposition appears too late. This is the main UX issue.
- Brand: black/white base is strong and distinctive; subtle blue/indigo accents can help clarify verification, source, and proposal states without turning the page into generic SaaS blue.

## Strongest direction

- Desktop: `desktop-mockup-v2.png` is strongest. It replaces the blank frame with a NIFYA-specific dashboard showing source alert, verification flow, proposal handoff, and next steps. It also integrates email capture into a horizontal proof band rather than a floating overlay.
- Mobile: `mobile-mockup-v2.png` is strongest after viewport cropping. It puts the headline first, preserves a strong CTA, and turns the product visual into a compact alert-to-proposal card instead of a blank phone-like rectangle.

## What changed visually

- Reframed the headline from passive monitoring to action: official changes become opportunities.
- Replaced generic/empty product mockups with workflow-specific UI: official source → NIFYA verification → alert → proposal workspace.
- Integrated source chips for BOE, DOUE, DOGA near the CTA so coverage is visible immediately.
- Reduced floating UI interference by placing email capture as a normal page band.
- Used calmer cards and proof blocks to support trust without adding unsupported claims.

## Implementation notes

1. Replace the blank hero visual with a deterministic React/CSS product preview card, not a static screenshot, so source/status labels can stay accurate.
2. Mobile should render headline and CTA before any large product preview; keep the preview compact in the first viewport.
3. Convert the floating email capture into an inline or sticky-bottom mobile component only after scroll; avoid covering hero content.
4. Add a small workflow strip: official source, verified, alert sent, proposal ready.
5. Keep copy grounded: avoid fake metrics unless backed by runtime data.
6. Use source chips for BOE, DOUE, DOGA, and “+ más” as trust anchors.
7. Give proposal-agent capability one early mention: “Abrir propuesta” or “Crear propuesta” from a relevant alert.
8. Keep NIFYA monochrome identity; use blue only as interaction/status accent.
9. Preserve existing CTAs: signup and contact/demo remain primary paths.
10. Test mobile at 390x844 specifically because that is where the current hierarchy fails hardest.

## Risks and constraints

- Generated mockups include illustrative text; implementation should use real product copy and actual capabilities.
- Do not use fake institution logos or unsupported source claims.
- The mobile v1 generation ignored the exact viewport and produced a long page; v2 was cropped to a true viewport for review.
- Product preview should be built from real components or controlled static markup to avoid text hallucination.