The current app.py module doesn't support any config options We could potentially support the following:

• --headless and --non-headless: Whether the user wants to open a headless(runs the browser session in the background) selenium browser session or not.
• --config <path/to/config>: If the user wants to specify a custom ${HOME}/.selemrc file.
• --no-join: If the user doesn't want to automatically join an ongoing meeting, rather be just notified about it.
• (CONTROVERSIAL) --cron <cron-time>: If the user wants the search to run CRON'ically at specified intervals without making a cron-tab himself?

Any other pointers are most welcome. 😀

Unlike auth.py, other modules do not currently leverage the benefits of Classes and data members, suppressing proper use of code-reusability and hampering code maintainability. We should wrap the respective functions inside Classes so that they can be reused globally with ease.

While automatically searching for ongoing meetings and joining them, the logic doesn't justify how to stay "joined-in" in the meeting. Rather, it quits the selenium browser session as soon as a meeting is joined preventing the user from staying in the meeting. This is a critical issue and should be resolved at the earliest.

We could potentially show a nice little welcome screen before starting the app. Listing down the app that is being run, its features and maybe a section to show the current configs that the app is loaded with(when we support this, see #4) and loading animation(?).
Oohh...and don't forget to use our special styles package for pretty printing. :)