# Thunkable documentation - issue: loses information fidelity **URL:** \ **Category:** Feedback\ **Created:** [September 6, 2017, 11:56am UTC](https://community.thunkable.com/t/thunkable-documentation-issue-loses-information-fidelity/7356 "2017-09-06T11:56:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![falcon74](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/falcon74/32/7513_2.png) [@falcon74](https://community.thunkable.com/u/falcon74)\ **Post date:** [September 6, 2017, 11:56am UTC](https://community.thunkable.com/t/thunkable-documentation-issue-loses-information-fidelity/7356/1 "2017-09-06T11:56:04Z")
Would like to take this opportunity to report what might be a potential issue with the way Thunkable Android documentation is written or organized, vis-a-vis MIT AI2 original documentation. I think Thunkable Android documentation is losing important information / fidelity, s.a. distinction between “methods” and “events”, while mixing them up, also with “parameters”. Take for instance: [https://docs.thunkable.com/android/components/social/phone-call.html](https://docs.thunkable.com/android/components/social/phone-call.html) , and compare it with [http://ai2.appinventor.mit.edu/reference/components/social.html#PhoneCall](http://ai2.appinventor.mit.edu/reference/components/social.html#PhoneCall) – we can note that, from Thunkable docs it is not clear as to what are methods and what are events, what are component parameters, but from AI2 docs it is quite evident. Hope that this is fixed (if Thunkable team agrees). ---
**Author:** ![albert](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/albert/32/4077_2.png) [@albert](https://community.thunkable.com/u/albert)\ **Post date:** [September 6, 2017, 6:38pm UTC](https://community.thunkable.com/t/thunkable-documentation-issue-loses-information-fidelity/7356/2 "2017-09-06T18:38:00Z")
Hi there. Thanks for your feedback. We made the change to simplify the documentation for our users since most of them won’t easily know what a “method” or “event” is. How does that distinction help you when building apps? ---
**Author:** ![falcon74](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/falcon74/32/7513_2.png) [@falcon74](https://community.thunkable.com/u/falcon74)\ **Post date:** [September 6, 2017, 6:42pm UTC](https://community.thunkable.com/t/thunkable-documentation-issue-loses-information-fidelity/7356/3 "2017-09-06T18:42:58Z")
Albert, Perhaps it is because I am returning to AI2 style development after a gap of few years, but this time with Thunkable, and haven’t explored Thunkable fully – but, back when I was using AI2, I remember that events had to be handled, so developer would create handlers for those events. Methods on the other hand, were called. The visual representation of the blocks, and what could be done with them was different. Has that changed ? Or I’m just plain rusty ! cheers ---
**Author:** ![albert](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/albert/32/4077_2.png) [@albert](https://community.thunkable.com/u/albert)\ **Post date:** [September 6, 2017, 6:52pm UTC](https://community.thunkable.com/t/thunkable-documentation-issue-loses-information-fidelity/7356/4 "2017-09-06T18:52:04Z")
Hi there. You are right – the blocks are different between methods and events for the reasons you’ve mentioned. I think it becomes obvious when you start building on the blocks but agree, it may be confusing if you are just reading the docs. Will have a think about it! Thanks for the feedback and welcome back to app building, Albert ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [November 8, 2024, 12:06pm UTC](https://community.thunkable.com/t/thunkable-documentation-issue-loses-information-fidelity/7356/5 "2024-11-08T12:06:17Z")