The most important mission with a m2m/IoT/whatever framework like VSCP is to make the world simpler for the end user. Yes for the “end user”, NOT for the developer. That said it is of course good if things are as easy as possible for the developer to.
If you are new to VSCP the system is always overwhelming. It is a big system with many possibilities, but the event is central, VSCP is after all an event based system, and when your data is on the VSCP standardized event format you can present it, store it, react on it or calculate on it in a standardized way. Any solution you come up with that handles events will become a reusable component. For you and for others if you share your work. For instance. If you make a software that diagram measurement value and your intention is to show temperature changes this same piece of software will be useful for someone else to display concentration variations in a fluid of a process industry by just changing the description of the diagram labels.
VSCP events have a class and a type that specify what the event describes. This is typically a “measurement” or “info” or “control”. Samples are
Class=10, Type=6 The event describes a temperature.
Class=30, Type=5 Turn on something
You can read all about them here