To my opinion there is no problem of this library interacting with WhatsApp, however I believe the library will be of far more value if:
1. it can send a message (start a chat) to any Whatsapp user without the need to do anything manually in Whatsapp.
2. it can receive incoming Whatsapp messages.
3. It can handle Whatsapp error messages (like reporting of non-existing user id numbers).
In my case I want to add Whatsapp functionality to my app for blind and visually impaired users, i.e. make a wrapper.
My app uses speech recognition, so the user could speak the name (or number) of the Whatsapp user and dictate the message.
If my app could monitor incoming Whatsapp messages then the TTS voice could automatically read incoming messages aloud, just like it already does with SMS messages (Ref:
http://www.artipal.com)
It wouldn't harm if Whatsapp briefly appears on the screen, as long as my app can automatically return back on the foreground within a few seconds, such that the user can touch the screen to speak a command or ask a question.
However, I have a feeling that I am asking too much and these functions are not implementable due to the limitations Whatsapp has imposed. As it stands, I don't really think the current library has much to offer, because: why type in a number and message in a B4A app if it cannot be processed by Whatsapp? One might as well directly access Whatsapp to do so. An intent to startup Whatsapp is all that is needed. If I am overlooking something then please tell me so!