Skeleton Loaders, Autofill, Optimistic UI: 5 App UX Tips Checked
By Matt Cullerton, founder of Mavric and Apso
A TikTok from @jploftofficial, the account of app development company JPLoft, lists five features to put in "almost EVERY app": skeleton loaders, autofill, optimistic UI, saved progress and friendly error handling. Most of the advice is sound, and autofill has the strongest evidence behind it. The one number in the video, that skeleton loaders make an app "feel 100 times faster," is not supported, and the only published head-to-head test found spinners did better.
Are skeleton screens better than spinners?
The video asks, "Why are we still making users stare at a spinning circle while something loads?" and says skeleton loaders make an app "feel 100 times faster and more polished."
Viget tested exactly this in October 2017 with 136 participants split across a skeleton screen (39), a spinner (39) and a blank screen (58). The skeleton group came last on every measure:
- 59% of skeleton users agreed the content "loaded quickly," against 74% for the spinner and 66% for the blank screen.
- 36% of skeleton users disagreed, against 10% for the spinner.
- Skeleton users estimated a longer wait (2.82 seconds against 2.41) and took longer on the follow-up task (10.54 seconds against 9.49).
Viget concluded that "skeleton screens aren't a silver bullet for increasing perceived performance and should be used thoughtfully."
Other evidence goes the other way. A 2018 paper by Mejtoft, Långström and Söderström at the European Conference on Cognitive Ergonomics found a skeleton screen scored higher on perceived speed and ease of navigation. Bill Chung's UX Collective write-up reports that skeletons animated left to right feel shorter than pulsing ones, though he says his samples are too small to be conclusive.
The results depend on the animation and the interface. No source supports "100 times faster."
Does autofill really reduce form abandonment?
Yes, and this is the best-supported tip in the video: "If I already gave your app my name, email, address, or any other information, please don't make me type it again. Use native autofill."
Native autofill is built into the platforms. On the web, the HTML standard's autocomplete attribute has a fixed set of field names, including name, email, tel, street-address, postal-code, cc-number and one-time-code. On iOS, UITextContentType values such as .name, .emailAddress and .telephoneNumber connect fields to iCloud Keychain AutoFill.
Google's Chrome team analysed address and payment forms across millions of page loads in December 2024. With autofill, time spent filling forms was about 35% lower and abandonment was 75% lower. Chrome notes this is correlational, since autofill users may already be faster.
Baymard Institute reports that 17% of US online shoppers have abandoned an order because checkout was "too long / complicated," within an average cart abandonment rate of 70.22% across 50 studies.
What is optimistic UI?
The video describes it this way: "Update the UI immediately, process the actual request in the background, and only reverse it if something goes wrong."
React 19, released on 5 December 2024, ships this as the useOptimistic hook. React's docs describe the rollback: "If the Action throws an error, the Transition still ends, and React renders with whatever value currently is." Because the real value only updates on success, a failure returns the UI to what it showed before. The revert the video asks you to build is now the default behaviour.
How do you save a user's progress?
The video says a half-finished form should never make users start over. On Android, SavedStateHandle in the ViewModel keeps values across system-initiated process death, and Android's docs name "input in text fields" as a use case.
That state has limits. It is lost if the user force-stops the app, swipes it out of recents or reboots. Putting a user back where they left off after any of those needs real persistence, such as local storage or a database.
How should apps handle API errors?
The advice is: "Catch the error, preserve their progress, tell them what happened in normal language, and give them a button to try again." That holds up.
The video's example is slightly off. It says users should never see "a 404 random backend message," and the description lists "a 404, 500, or random backend message." A 404 is a client error (the requested resource was not found), while a 500 is a server error. The difference tells a developer whether to retry or fix a route, so it is worth keeping separate in error handling.
Who is JPLoft?
The presenter says he has been "building apps for over 10 years," and the on-screen text says "10+ years." JPLoft's homepage claims "16+ Years of Experience" and "1250+ Projects Successfully Completed," with headquarters in Denver and offices in the UK, India, Australia and Saudi Arabia. Its Clutch profile lists a 2010 founding, 50 to 249 employees and a $10,000 minimum project. Rahul Sukhwal is listed as founder and CEO. The presenter in the video is not named.
The video promises five features, then ends on "number six, bonus," which is a prompt to follow the account.
Bottom line
Autofill and optimistic UI are well supported, and both are now built into the platforms. Saved progress and plain-language error recovery are sound advice, with limits on what instance state survives. Skeleton loaders are a reasonable pattern whose effect depends on how they animate, and the one published A/B test found spinners felt faster.
Sources
- The TikTok from @jploftofficial - the source video
- A Bone to Pick with Skeleton Screens, Viget - the 136-person test
- Everything you need to know about skeleton screens, UX Collective - animation direction findings
- The effect of skeleton screens, ECCE 2018 - the counter-finding
- HTML Standard: autofill - autocomplete field names
- UITextContentType, Apple - iOS AutoFill values
- Autofill in action, Chrome - fill time and abandonment data
- Cart abandonment statistics, Baymard - checkout abandonment reasons
- useOptimistic, React - optimistic update hook
- React 19 release - release date and new hooks
- Saved State module for ViewModel, Android - SavedStateHandle
- 404 Not Found, MDN - status code classification
- JPLoft homepage - company claims
- JPLoft on Clutch - company profile
- Rahul Sukhwal on LinkedIn - JPLoft's founder
- Jploft Solutions Private Limited - the Indian entity's registration
Published September 24, 2026. Based on a TikTok by @jploftofficial. Full video notes (markdown)