# The Refresh Test

DevFeed: [The Refresh Test](<https://devfeed.tech/articles/the-refresh-test-40626.md>)

Original publisher: [Read original article](<https://eviltrout.com/blog/2014-04-10-the-refresh-test/>)

Published: 2014-04-10T00:00:00Z

Content type: opinion

Language: en

Sources: [Robin Ward](<https://devfeed.tech/sources/robin-ward.md>)

Topics: [Ember](<https://devfeed.tech/topics/ember.md>), [Website](<https://devfeed.tech/topics/website.md>), [browser](<https://devfeed.tech/topics/browser.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [browser](<https://devfeed.tech/tags/browser.md>), [ember](<https://devfeed.tech/tags/ember.md>), [fields](<https://devfeed.tech/tags/fields.md>), [form](<https://devfeed.tech/tags/form.md>), [make](<https://devfeed.tech/tags/make.md>), [reload](<https://devfeed.tech/tags/reload.md>), [required](<https://devfeed.tech/tags/required.md>)

## AI overview

The article argues that web applications should preserve form data and tolerate page refreshes. It uses frustrating account-creation and online checkout experiences to illustrate the problem, then discusses how Ember App Kit's live reloading encouraged the author to make an application refresh-resistant.

## Source excerpt

How many times has the following happened to you? You go to a web site and it asks you to create an account. You fill out a form with all the obvious fields and hit submit. The page refreshes and shows you the form again. Phone Number is required Well, that's annoying. There was no indication that the site needed your phone number. You prefer not to give out your phone number to every web site, but this one is run by a company you trust, so you scroll down and fill it out. You submit the form again.