SShortSingh.
Back to feed

Designing Empty States: Decide What the Page Must Explain Before the Illustration

0
·7 views

An empty dashboard can look unfinished when blank, yet an oversized illustration can make a serious app feel like a greeting card. The article argues that designers should first determine what the empty page needs to communicate. Using a bookmarks app, it contrasts a new-account state, which calls for a prompt to save a first link, with a no-search-results state, which calls for different guidance and a clear action. Illustrations should be tied to a specific state and kept simple, with a concise brief and a generation prompt suited to that context. Designers are advised to review the visual at its actual display size and to keep essential instructions in editable HTML text rather than inside the image.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Giving AI Agents Access to Data Raises Security Risks Developers Must Address

A DEV Community article argues that AI agents with tool access to databases, email, and business systems create new security challenges for developers. It uses a customer-support CRM example to illustrate excessive agency, where an agent is exposed to far more capabilities than its task requires, such as deletion or bulk export. The piece explains that external content like customer notes can carry hidden instructions that redirect an agent, a risk known as indirect prompt injection. It recommends limiting tools to the minimum needed per role, using narrowly scoped credentials, and treating all external data as untrusted. The article frames these measures as essential as developers move from chatbots to autonomous workflows.

0
ProgrammingDEV Community ·

Five NGINX flaws patched; exposure depends on config directives, not version alone

A set of five NGINX vulnerabilities has been addressed in a single release, but each depends on a specific configuration directive being present. The article uses a ZoomEye search returning about 313 million NGINX-fingerprinted assets to illustrate the scale of the problem, while stressing that this counts hosts exposing an nginx fingerprint rather than confirmed vulnerable servers. A separate CVE-based search returned zero results, showing that CVE indexing cannot replace product and configuration review. The author recommends enumerating fingerprinted hosts, then checking their configuration output for the five triggering conditions. Vendor advisories from NGINX and F5 are linked for the affected cases.

0
ProgrammingDEV Community ·

Homelab security console warden adds a five-minute demo setup

The developer has released warden, a homelab security console that reads logs, scans machines, and proposes bans and patches that the user must approve in Discord. A setup guide lets users try it on demo data in about five minutes, without connecting it to any real systems. The guide is tested weekly via a GitHub job on fresh Ubuntu machines, with support for Ubuntu 24.04 and Debian 13. Warden also offers a REST API and MCP endpoint that let AI agents query its status, though every tool is read-only and cannot ban or patch anything. A check command reports which features are working and what to fix, and the full guide is available on GitHub.

0
ProgrammingDEV Community ·

AI Reshapes Software Hiring, Hitting Entry-Level Developers Hardest

Software developer employment has not collapsed, but hiring is shifting toward senior and AI-related roles. US software job postings remain well below their February 2020 level yet have risen roughly 15% since early 2025, with most of the gain in senior positions. Research from Stanford economists using ADP payroll data finds employment of workers aged 22 to 25 in AI-exposed jobs is about 19% below its expected trend, mainly through fewer hires rather than layoffs. The Bureau of Labor Statistics still projects 10% growth for software developers over the next decade, while the narrower computer programmer role is expected to decline. Analysts continue to debate how strongly AI is driving these changes.