Should the template set up logging?

[filiph]

Logging is one of those things every app will need sooner or later. Should it be set up in the template? To what extent?

• No logging in the template
• A comment in the appropriate place (main()) saying something like: "Here's where you can set up your logging and error reporting" (plus link)
• Use pkg:logging but do not gather the messages
• Use pkg:logging and gather the messages in main through Logger.root.onRecord.listen, printing them
• Use some other approach

[fullmers]

Since most projects will need logging, I think it should be included with a simple example.

[PiotrWpl]

I think that it would be a good idea to show that there are better solutions for logging than a simple print() command. Even showing that there is something like log() will be useful for most of the new users.

[escamoteur]

Maybe not only logging but also a global exception handler?

[chimon2000]

Perhaps a logging abstraction over print that can be easily overridden?

[nerder]

This is totally needed, we are struggling on implement this on a mature app. Logging is that kind of thing that is very easy to plug in in the beginning, not so easy to do at later stage, so up for it. 👍🏼

[sfshaza2]

Yes to logging, if I get a vote. :)

[asidt]

Yes to logging, possibly a complete but simple example on how to set it up correctly

[neiljaywarner]

Flimber or similar - especially if you can do LineNumberDebugTree - jump to line in source https://stackoverflow.com/questions/38689399/log-method-name-and-line-number-in-timber - it's like magic

Timber is practically the gold standard on Android

especially nice would be a link to a dead simple crashlytics tutorial and a way you you can turn on with a few lines