Scorpius, a thought below for your consideration.
You don't have to do it of course.

Perhaps you could split Yappari to an engine binary & a UI lib*.so.
A set of API interfaces would be required at both sides.
The engine would call callback functions on Whatsapp protocol events. Callback implementations on the UI side then need to be available for the engine to call.
Likewise, the UI would call callbacks & the engine have corresponding callback function implementations.

You could then keep the engine/protocol code & outsource the bigger problem (UI, which takes up most of your time & typically any dev project's time) to the community.

Implies lotsa change to your code unfortunately, if it hasn't been implemented in such an architecture. But the benefits are great (imagine just asking for an interface & someone else does all that pain for you )

You get the drift, being an experienced coder n all.

& I'm still hoping you'd implement ability to let Yappari accept an IMEI specified into yappari config file of course.. :P Wishful thinking.

kh