Everything has an Interface. The interface of a function is it's name, it's arguments and it's return types. The interface of a TV is it's remote control, and the interface of a car is it's steering wheel, gas/break pedals, etc. When using it like intended, we don't directly interact with the internals of a TV (circuitry), nor with the internals of a car (engine). I have a video on Interface-First Programming if you want to know more. You can think of the interface as the thing you are interacting with, which is different from the things that are behind that, which you are not directly interacting with. The interface exists because it enables a use-case: the engine of a car can run by itself, but it's not useful yet, just as a TV can run without a human watching it, but that's not useful. We added a steering wheel to an engine because humans are using the engine for a very specific thing; going somewhere. The interface encodes it's use-case. A Facade is an extra layer (an extra interface) in between a call site and an implementation (e.g. a function, file, class, or service). This extra layer can be there because you don't like the interface that the implementation offers by itself, or it can be there because you don't want to directly depend on the interface of the implementation. A Facade has, like all functions/classes/files, also an interface: it's names, arguments, return types, etc. Anything you directly interact with from the call site.

@@branvandermeer So, if i were to program an extra layer between the firebase API and my web app because I didn't like the convoluted process for image uploads and wanted to simply function calls with a one time configuration, that would be a facade.

@@benflightart yes!

@@branvandermeer thanks for helping me understand!