What references from New Zealand reveal
New Zealand’s three references show why a national design list should include different visitor intentions. Resn’s public presentation points toward interactive brand experiences. Gladeye connects narrative with websites, products and digital experiences. Springload publishes work involving an airport, a type foundry and a wildlife destination, where current information and service clarity are as important as atmosphere. These official social images introduce the studios’ public visual language; they are not screenshots of every named case and do not prove accessibility, speed or commercial results. Judge each reference through the audience’s next action. A campaign experience needs a route into readable content and a useful conversion after the visual hook. A narrative-led company site needs enough structure for visitors who arrive on a specific service or article rather than the home page. An airport or visitor destination needs resilient schedules, alerts and content governance. New Zealand teams may also serve international audiences, so test time zones, language expansion and support ownership rather than assuming a local launch is monolingual or static. The best lesson from this set is to connect expressive craft to the mundane states that keep a website trustworthy: loading, empty data, errors, content expiry and editor handoff.
These references are presented for design analysis and inspiration. This is not an audited ranking, a quality certification or a claim that Dardo created or measured the featured work.
Three website references to study
01 / Resn
Resn studio presentation
What stands out
The reviewed record is an official social presentation image: Presentation image published by Resn. For Resn, it should be read as the studio's own presentation, not as an independent audit or a complete capture of every interface state. Resn’s current offer centers on brand stories, content and digital experiences. Its public company profile lists Wellington and Amsterdam. Review it when the brief calls for a creative interactive production, and request a relevant recent case rather than choosing by reputation alone. Define the content access, mobile fallback and maintenance needs that surround the central experience. In this showcase, its useful role is to focus discussion on story, public information and post-launch editing. The image can establish a visual direction and the official source, while a buyer still needs to open a relevant live case, verify Resn's precise contribution, and test the content, mobile behavior, accessibility and operational states that the static record cannot reveal.
Translate this reference into a testable requirement about story, public information and post-launch editing. Ask Resn: “What can visitors still read and do if the main interactive scene does not load?” Then request the closest live example and its exact role. Put Resn's answer into the proposal as named pages or states, content owners, responsive and accessibility checks, acceptance evidence and post-launch responsibility. Do not copy Resn's surface or assume the presentation proves a result; use the source to sharpen what your own users must understand or complete.
02 / Gladeye
Gladeye studio presentation
What stands out
Presentation image published by Gladeye is the subject of this reviewed record. Because it is an official social presentation image, it documents how Gladeye presents its work rather than proving performance, accessibility or authorship of every visible element. Gladeye describes an Auckland-based creative digital agency connecting storytelling with websites, experiences and products. Its offer is relevant when a business needs a strong narrative as well as an interface. Ask for a recent case matching your content and operational needs, then define how the storytelling will lead visitors toward a useful commercial action. For this market comparison, inspect the asset through story, public information and post-launch editing. Follow Gladeye's official link to a comparable live journey, ask which team and collaborators delivered it, and check ordinary pages, errors, confirmation and editing. For Gladeye, those steps preserve the visual lesson without asking a promotional still to carry evidence it does not contain.
Use Gladeye's image to brief a decision, not to prescribe a copy. The relevant fit is brand storytelling and digital experiences. Ask: “Which part of the story helps visitors evaluate the offer, and how will that action be measured?” A useful response from Gladeye should name the people, workflow and live evidence behind it. Record the requirement alongside story, public information and post-launch editing, then test it with realistic material on mobile and desktop. Confirm who at Gladeye implements, verifies and maintains the behavior so the visual ambition survives ordinary use.
03 / Springload
Springload studio presentation
What stands out
This example uses an official social presentation image described in the evidence library as: Presentation image published by Springload. The format of Springload's record is disclosed because a presentation image and a live-project audit answer different questions. Springload’s Wellington portfolio includes Wellington Airport, Klim Type Foundry and Zealandia, with strategy, content, design, development and maintenance services. These cases provide concrete ways to compare live information, commerce and visitor discovery. Review the content workflow and accessibility approach alongside the visual work, particularly when information must remain accurate after launch. Its place in this collection is therefore analytical: it helps a buyer examine story, public information and post-launch editing. Treat Springload's composition as a starting point, then verify the current site, the agency's exact role, responsive and keyboard behavior, realistic content, failure states and the people responsible for updates after launch.
The buyer lesson is to connect useful public-facing websites and services with a concrete acceptance task. Put this question to the studio: “How will staff update time-sensitive information, and what happens when the live data source is unavailable?” Compare the answer with your needs around story, public information and post-launch editing; ask for a comparable live walkthrough and disclose any collaborators. The contract with Springload should identify content, components, data or integrations, test conditions, ownership and support. That is stronger evidence than choosing by the still image alone.
Questions before you choose
What makes a New Zealand website reference useful for an international project brief?
A useful reference exposes a transferable decision rather than merely a local style. Record the intended audience, the task shown, the content that must stay current and the studio’s confirmed role. Test whether the live project offers readable content when interaction fails, whether mobile navigation preserves the story, and whether editors can update urgent information. For an international brief, add language ownership, time-zone review windows, currency or booking rules where relevant, and the route for support after launch. Compare those facts with your own operating constraints. The location can help identify collaborators, but it does not prove that the same scope, team or technical approach will apply to your project.
What these examples show together
The shortlist becomes useful when Resn, Gladeye and Springload are treated as three operating models. Resn invites scrutiny of interaction and fallback. Gladeye prompts a discussion about how story becomes navigation and action. Springload brings content operations and public information into the visual review. Each reviewed asset is a studio-published social image, so use it as an entry point and confirm the live behavior independently. A buyer should leave the inspiration session with a selected audience task, a content owner, a mobile and accessibility test, and a support plan. Without those decisions, the visual reference remains attractive but too ambiguous to guide a build. Turn the selected principle about interactive production, narrative direction and resilient public information into a scenario that all finalists must demonstrate. Record the expected content, devices, owners and recovery state. This closes the gap between admiring the New Zealand examples and deciding who can deliver the system under the proposed scope.
How to use this collection
Use the references to discuss hierarchy, content, interaction and production choices with your team. A strong visual direction still has to fit the audience, editing workflow, accessibility requirements and business task in your own brief.
This is an editorial inspiration collection, not an audited ranking or a claim that Dardo created or measured the featured work. Names, images and links are credited to their published sources and were reviewed on the date shown above.
Plan a project with Dardo
Plan a project for New Zealand
Choose a review date and a time in Bogotá to see the corresponding local time. This is a planning aid, we’ll confirm availability when we reply.
Pacific/Auckland — Representative time zone; some countries have more than one. Check the actual city and agree on a working window. Dates include seasonal clock changes through your browser’s time-zone data.
Budget currency to discuss: NZD. The project calculator lets you enter your own rate. It does not convert exchange rates.
Let’s make it happen.
Send your result and project details directly to Dardo. We’ll review them and reply to your email. Review the included details below before sending.
Prefer email? hello@dardo.studio
Sources & further reading
Sources behind this guide, with further detail from the original publishers.
- Resn studio presentation — official source resn.co.nz
- Gladeye studio presentation — official source gladeye.com
- Springload studio presentation — official source springload.co.nz