Well, not necessarily. Appium might be useful, but it depends on how the app under test is built. If its UI components have attributes or properties that define its state (color, selected/highlighted or not, enabled or not, location coordinates, etc.) then you can validate whether those values are correct or not with Appium. But for testing that it is actually "rendered" visually correct in the device/simulator, you would need a tool like Applitools.
But Applitools, if I'm not mistaken is for validating the visual aspects, it won't "drive" your application into the desired states and workflow screens, therefore you still need Appium to do that part of it, and call Applitools on the visual state validation parts.
If you wanted a single tool that kind of does the validation and driving in one (although that may or may not be best), you could look at Sikuli and Experitest's tools, that drive app by image recognition of UI elements.
