Ultimate Frame Data

MetalMusicMan

About this app

11-19-2023 -- The crashing issues have been fixed, huzzah! The issue was... *drumroll* ...the CSS property "word-break" being set to the deprecated value of "break-word". Absolutely insane. Bonkers. Unhinged. Googlepls. W H A T?!

--- --- ---

Startup, Active, On Shield advantage/disadvantage, Out of Shield Options, and more! Now includes hitbox images! Visit https://ultimateframedata.com for the web version (IOS users can add to home screen).

See something that needs fixing? Tweet me @MetalMusicMan_ You can follow @ultframedata if you only want UFD updates.

*Internet Connectivity not required for Frame Data or general app usage, but IS required to view Hitbox images*

Ratings and reviews

This is probably one of the best most essential applications I have on my phone... Seriously lol. If I'm picking up a new character or just want a quick refresher on some firm data or other information, it's quick convenient and accurate. The illustrations of the hitboxes are helpful, out of shield options and start up times have helped me become a better player.

Its very handy and quick to use! Sometimes I feel like I want to see more moves at once, but I can easily do that on the website if I'm at home! Any time if I use this while out, it makes the search for info easy thanks to the search option and drop down menus. EDIT: Omg the addition of hitbox visualizations makes this app even more useful! Normally I'd have to download the visualizations to view on my own or go to google docs folders, but its all coveniently in one place! It's also toggleable

Its very easy to find frame data for any character, and I pop open the app or the website if someone (or me myself) has a question about frame data. The only thing is that I wish I could favorite a character or two if they're characters I main and or want to know the matchup on so they appear at the top of the list. The search option is nice though, so I won't complain if that doesnt get added

What's new

Removed CSS "word-break: break-word;" property that was apparently the cause of the crashes (due to a Webkit rendering engine bug). LOOOOL, what a wild ride that was.