Dynamic Communication API
Dynamic Communication API
The Dynamic Communication API project aimed to provide a solution for automating
communication through various messaging platforms, primarily focusing on WhatsApp.
Throughout the project lifecycle, four distinct plans were proposed and implemented to address
the evolving requirements of the clients. Each plan represents a progressive iteration towards
fulfilling the client's objectives.
----------------------------------------------------------------------------------------------------------------
Project Plan 1:
Objective: Automate WhatsApp messaging through Microsoft Excel with Visual Basic.
Implementation:
Developed a solution leveraging Microsoft Excel's developer mode and Visual Basic scripting
to automate message sending on WhatsApp.
Successfully cracked the automation process, enabling messages to be sent to unlimited phone
numbers without the need to save them.
Limitations:
Inability to send images, files, videos, and documents due to restrictions imposed by
WhatsApp's policies.
----------------------------------------------------------------------------------------------------------------
Project Plan 3:
Objective:
Overcome webpage redirection and backend code requirement using PHP and cURL.
Implementation:
Developed backend functionalities using PHP and cURL for message automation.
Implemented a user-friendly frontend with input boxes and a send button to interact with the
backend.
Utilized Twilio API for message mediation, enabling both text and media file sending.
Limitations:
Upgrading Twilio account required for file automation.
Mandatory registration for Twilio recipients.
Real time output:
Project Plan 4:
Objective: Replicate a YouTube video project demonstrating WhatsApp-like chat inbox with
media sharing.
Implementation:
To do this, Solution suggested by them only !!
Successfully replicated the YouTube project, creating a chat inbox with media sharing
capabilities.
Achieved the desired functionality of sending text messages, images, and PDFs, able it not in
real-time.
Limitations:
Lack of real-time message sending due to localhost hosting.
Requested additional pages such as a home page and about us page couldn't be implemented
due to constraints imposed by the backend JSON hosting. This limitation stemmed from the
project being sourced from a YouTube tutorial restricting modifications beyond certain
functionalities.
Output:
Conclusion:
The journey through the four project plans highlights our persistent efforts to address client
requirements and overcome technical hurdles. Each iteration aimed to tackle specific
limitations encountered previously, showcasing our adaptability and problem-solving skills.
Despite challenges, we successfully implemented solutions that met project objectives within
the given constraints. The considerable time, effort, and technical expertise invested in
delivering tangible results are evident throughout the project's progression.
Therefore, it's crucial to acknowledge the thorough documentation and successful
demonstrations of our implemented solutions, underscoring the significant effort and
achievements made in this endeavour.