Our application basically has 3 parts to it; let’s look at each one in detail below:
I. Front End or Client Side Android app
The steps below will explain the working of the APP when it will be used by our Buddy at the
customer’s retail outlet(KFC, Mcd etc.).
Step 1: Our Buddy will put in his id and password (Location Specific) to gain access to this app.
(We are doing this so later on when we want reports in auto-mode or manual generation of a
specific outlet; it can be done)
Step 2: Our Buddy will click next and move on to the next screen. This will have a dropdown
containing names of different outlets that our Buddy can switch to in the same area. (Like in
Powai, he can work in KFC, Mcd, Yo China etc.)
Step 3: This screen will be designed according to the outlet with our logo etc. Here our customer
enters his mobile number which will be validated like on [url removed, login to view] which is easy to do and
will flash his service provider like Idea or Airtel etc. Also, XYZ can add personal details like
birthday, anniversary, etc. which will be optional. Here, the cell number and bill number will
provide validation (multiple entries for the same cell number and bill number will not be
allowed). And he clicks next.
Step 4: Here our Buddy inputs the Bill No. (This also can be validated depending on the number
of digits used by the outlet as it will also contain that outlet’s code (Customizable validation
possible) (This is necessary to avoid further errors) and Bill Amount of the customer, XYZ. And
Step 5: This screen shows XYZ’s history. This screen will be divided in two parts; one showing
all offers and the right one showing the offers he is eligible for .
II. WEB Admin Dashboard or Portal (Server Side)
Again this has three parts and will be customized depending on our experience and needs. This
will be accessible from a computer and should have the same domain name as the app (we will
need to buy this domain name) and some storage space from Godaddy etc. The Android app can
have an admin button but it has limited use and it is generally not advised.
There are two roles viz. admin and service. This is a simple white screen for us and it
doesn’t need to be aesthetically well designed, probably just our logo. If admin
credentials are entered then the individual has access to everything that is possible like
changing coupon codes, seeing coupons given by comparing to the SMSs send etc. If a
service credentials are entered, then this Buddy will have limited access and can only
generate various reports as defined by us to be studied by our BD or BA guys. When we
see that we need some new reports for our analysis, we will generate a fresh SQL Query
through the admin access panel which generates reports after accessing our database. If a
report is frequently used then we can add it as a button for our Buddy with service access.
There can be errors like (wrong entry by our Buddy or user, validation failure as mobile
number was wrong at first, etc. All these errors need to be fixed in our system) Some
Database access softwares like SequelPRO can be used by the admin to check for
common errors. We can create a UI for the user with service access to look into it or it
can also be automated later on.
Daily report generation will be done by automated services (maybe cron jobs) as we will
have coded common reports with buttons like monthly report or daily report of an outlet
depending on our study. Here, if we do not get the access to generate coupon codes from
Mcd then we will have to manually enter coupon codes; this is optional and will make
our system stronger. Or else a specific coupon given out can be compared to the coupon
code sent in the SMS to make sure that coupons are not misused.*