This might be a little elementary for anybody with a computer science background, but for the rest of us, here’s a primer to help understand the concept of EVENTS.
A computer doesn’t actually do anything on its own, even though it might seem that way.
No, what a computer actually does is wait.
Think about it: when you create an app in Method, the app isn’t going to start “computing” or performing processes all by itself. The Method app, like your computer, is waiting. And it is waiting for an event.
Think of it like waiting for your birthday to come. The birthday is an event and you are waiting for it to occur. For Method, the events it waits for is more mundane. It waits for a user to do something.
For example, if the user clicks a button on the screen, a click event is triggered, and that means the user has effectively poked the app and said “okay, time to do something!”
That “something” is what we call an ACTION.
So to recap, an event is something a user does in an app that tells the app it needs to take some sort of action. You can find a full list of the events available in Method right here.