Updated date:

Currency Note Recognition

Thank you for visiting my profile! I am dedicated to inspiring innovation through evolving to meet the latest technological demands


The modern world has brought its biggest fruit Smartphone, which has completely changed the way technology used to work for common people. Even the illiterate and visually impaired people are using the Smartphone in their daily life and getting the benefit out of it.


According to Pakistan National blindness and visual impairment survey (Nov 2006) 1140,000 people were visually impaired or blind. According to Eye Surgeon Dr. M. Shahnawaz Munami, Community Ophthalmologist and Patron in Chief of Disabled Welfare Association, Karachi around 6 million people in Pakistan are suffering from partial blindness (2013). This figure has reached a gigantic figure of 7 million in 2016, which is 3.2 % of the total population of Pakistan.

The biggest dilemma in Pakistan is that no effort has been made for visually impaired people to recognize currency notes using any simple device or mobile’s camera.

So we are trying to solve the following problems in Pakistan

  1. There is not a single application that can detect Pakistani currency notes using a mobile phone camera.
  2. There is no auditory solution for Pakistani currency note to be detected by the mobile phone camera.
  3. Dependence of visually impaired people on other people usually their family for shopping.
  4. Failure of state bank of Pakistan to provide such a solution; State bank of Pakistan releases an application and its only purpose is to tell you about the features of the currency note.

State Bank Of Pakistan

State Bank Of Pakistan

State Bank Of Pakistan

This application failed to address any problems of users and received pathetic reviews. All the Pakistanis complained that this information is basic known to everyone. This failed to even fulfill one request by all Pakistanis that was to detect Pakistani currency notes.

Our project targets this cornered segment of society especially visually impaired people so they can become independent instead of relying on other people for recognition of currency. The project when developed would prove to be the biggest tool for these people and they would be able to recognize currency, on their own. The auditory solution would enable them to listen clearly and distinguish between different currency notes based on their features.


Scope of project revolves around recognition of currency note, transmitting it in auditory voice. Primary target of our application is to produce the first auditory solution of currency recognition for Pakistani Currency notes using mobile phone camera.

Definitions, Acronyms and Abbreviations

RECOGO: it has been derived from the word of recognition and it is the name of our application as well which we have developed

Visually Impaired: partially or completely blind people.

Overview Statement:

Our project aims at developing an application for visually impaired and common people so they can recognize Pakistani currency using Smartphone’s camera by audio voicing. Using the Smartphone’s camera is not only economical but will also help them to become independent in life. For this we want to collaborate with government of Pakistan to at last work on this big problem and become the beacon of hope for such people.

Goals and Objectives:

This android application will be available free on play store from where it can be downloaded easily. This application will be available 24/7 and will be free of cost.

The main objectives of our application are given below:

  • The main objective of our application is to detect Pakistani currency notes.
  • Our second main objective is to provide auditory solution after detection of these currency notes.
  • We want to combine the detection of currency notes and auditory solution in this single application.
  • Make sure that this application is free so any one might use it without any problem.
  • Implementation of this system all over Pakistan with the help of state bank of Pakistan.

Elaboration of our three main objectives is given below.

Recognize Pakistani Currency Note

There is not a single application in Pakistani which can recognize, transmit and differentiate currency notes. Our first objective is to recognize currency notes based on their features.

Auditory Solution

After recognizing and differentiating between currency notes we want to provide an auditory solution in our application. The application will use speakers of mobile to explain clearly which currency note has been scanned.

Implement this system in all Pakistan with the help of State Bank of Pakistan:

We want to collaborate with collaborate with state institutions like State Bank of Pakistan to refine this app and make sure that it works professionally. We will also make sure that this app is provided to everyone and an awareness campaign is started all over Pakistan.

Tools and Technologies:

Software Requirements:

The main software components which we are going to use are given as follows

  • Android Studio:

We will use Android studio to develop an Android application.

Hardware Requirements:

  • Laptops:

Laptops are the major component of our project to run development tools.

  • Smart phones:

We need Smartphone to develop the project and check our progress and test our product.

Software Requirement Specification

Functional requirements



Capturing the image

First requirement of our application is to capture the image of currency notes using mobile phone camera.





Features extract

After capturing the image, the features of currency notes are extracted.





Features match

The extracted features are matched with the already existing features which have been stored in database. This is very important for understanding which currency notes are being scanned. After matching the system will understand and give you the desired results.


Auditory solution

Our application provides auditory solution, for the currency notes.

Non-functional requirements




Reliability of our application is very good but it also depends on the quality of your currency notes.






Capacity of our application is to process one currency note at one time. After one currency note is processed other currency note can be given as input.it supports only android smart phones.


System Requirements

For this application we need an android phone with minimum 15 mega pixel back camera.






It will be available 24/7 and may even run without internet. Its application will be downloaded and afterwards used.



Application is efficient if the currency notes are of good quality and so is the camera.



Application can be used in every android smart phone and can be transferred easily from one smart phone to another one.

Domain Requirements

Domain requirements reflect the environment in which the system operates so, when we talk about an application domain we mean environments such as train operation, medical records, e-commerce etc. Domain requirement reflects the characteristics in that particular domain, our domain is image processing so all the requirements are of image processing. All the terminologies and statements revolve around this domain. So while dealing with it we would be capturing image, checking whether image is of currency note or not. These all requirements remain within this domain. Figure below shows some of the important points within the domain of our project:

  • Image processing
  • Capturing Images
  • Processing Images
  • Color Domination

Use cases & Usage Scenarios:

Use case Diagram:

Use Case Diagram

Use Case Diagram

Use case Scenarios

Case ID.UC:1


Open App




User Will Open Application to Perform Note Detection


User Should Have Installed App Already


User Should Have Light Source

Case ID.UC:2


Adjust Camera




Adjust the camera exactly above the Currency note, so that camera may focus the Currency note.


Camera is already loaded

Post Condition

Object is detected, that it is currency note or another object

Success Scenario

Currency note is successfully detected.


Object must be currency note.


Will be detected successfully if currency note.

Case ID.UC:3


Capture Image




Tap on Camera screen To Take Picture


A Currency Note.is detected


Auditory solution is provided after recognizing currency note.







Planning the Project


In this chapter, we will discuss about various methodologies that can be adapted to make this project to completion. We will plan time scheduling for our task or activities on weekly basis and then finally we will evaluate our project success. We as a team will approve all decisions related to project planning. We also plan to control risks that might occur during project completion.

Research problem:

People with impairments have been always neglected in our society. There are multiple problems which these people continue to face even with the advancement of technology. The biggest problem which we identified was the dependence of these people on other people for their basic needs like shopping, transactions and other money related issues. With more than 6 million people in Pakistan suffering from partial blindness, we have taken up the issue of money related problems for this cornered segment of society. The main problem they continue to face is identification of currency notes with their eyesight if they need to even count their currency notes they need to depend on anyone to perform this simple operation for them.

Pakistan National blindness and visual impairment survey (Nov, 2006) gives a figure of 1140,000 people who were visually impaired or blind. According to Eye Surgeon Dr M. Shahnawaz Munami, Community Ophthalmologist and Patron in Chief of Disabled Welfare Association, Karachi around 6 million people in Pakistan are suffering from partial blindness (2013). This figure has reached an exponential growth of 7 million in 2016, which is 3.2 % of total population of Pakistan.

What factors contribute to the presumed effect?

The biggest factor which has added our interest in this project is the non-seriousness of the governments to help these people in any way possible. Our governments have never paid heed to the woes of these people who continue to raise voice for their rights but always remain unheard. Their protests and rallies continue to become headlines in the national and international newspapers that are always keen to look for an opportunity like these.

One more thing which remains a source of concern for us is the behavior of State bank of Pakistan which has not taken this problem seriously. The only application developed by State bank of Pakistan just explains the features of currency notes and does not even recognize currency notes. The reference of this application has already been given in first chapter and this has been explained in detail. The picture of this application has been provided along with reviews of people.

In the western world these problems are no more thanks to the advancement of information technology. This problem has been rationally solved using different applications that prove to be a handy application for visually impaired people because smart phones are now common irrespective of your status. Now smart phones have evolved from being a luxury to necessity. So solutions in form of mobile applications are no more a dream now.

Our assumptions and propositions:

We believe that our applications is the first step in the right direction. It is the first drop of rain and if this product is enhanced it can prove to be the best companion for such people. This application is highly scalable and can be developed into a robotic eye.

Previous Research:

So, we are conducted a survey to understand different aspect of market and what people thought. For this purpose 50 surveys were conducted from different sectors of society including students, teachers, employers and more than 30 surveys from these 50 were from visually impaired people. This is the prototype of survey and the results are also mentioned below.

1 Do you use smart phone?

  • Yes
  • No

Answers given: 99% people in our survey used smartphones.

2 Have you ever downloaded apps for your device?

a) Yes - Always Free

b) Yes - Always Paid

c) Yes - Free & Paid

d) No

Answers given: 90% of people use free applications and 10% use for specific purposes.

3 Do you want such an application which can detect currency notes especially 100, 500 and 1000?

  • Yes
  • No

Answers given: 40% of people replied they required and 90% of visually impaired people told us that they required our application.

4 Do you know about such an application which can perform this task?

  • Yes
  • No

Answers given: Nobody knows about such an application.

5 How much do you think our application is user friendly?

1 2 3 4 5

Answers given: 90% of people required it was extremely user friendly.

6 How much would you like to pay for such an application?

a) 100 rupees for 50 checks

b) 200 rupees for 200 checks

c) None of above

Answers given: All the people wanted this application free of cost.

7 How often would you use such an application?

a) Often

b) very often

c) Few times in a month

d) Every time

Answers Given: Most of the people replied they would use it often.

8 What’s your age?

a) 15-20

b) 21-25

c) Above 25

Answers given: Most of the people were of age 21-25.

9 What’s your marital status?

a) Married

b) Unmarried

Answers given: There were both genders, it was mix.

10 What’s your monthly household income?

a) Below 20K

b) 20k-50k

c) Above 50K

d) Student

Answers given: Most of the people’s household income was 20k-50k.

11 What’s your education?

a) Metric

b) Intermediate

c) Under-graduate

d) Graduate

e) Did not receive formal education

Answers given: Most of the people were educated.

12 What’s your employment status?

a) Student

b) Shopkeeper

c) Business

d) Unemployed

Answers Given:

State your email address (optional if you feel comfortable)_______________________

Answers given: Most of the people avoided this question.


Methodologies are general approaches for organizing a project into activities. They help the project manager and his or her team to decide what work should be done and in what sequence to perform the work.

Available Methodologies:

  1. Opportunistic approach: In the opportunistic approach, developers keep on modifying the software until they or their users are satisfied.
  2. Waterfall Model: It is a classic way of looking at software engineering that accounts for the importance of requirements, design and quality assurance. The waterfall model suggests that software engineers should work in a series of stages. Before completing each stage, they should perform quality assurance (verification and validation) so that the next stage can be built on a good foundation.
  3. Phase release Model: The most important change is that it introduces the notion of incremental development. It suggests that, after requirements gathering and planning, the project should be broken into separate subprojects, or phases. Each phase can then be released to customers when ready. Parts of the system will be available earlier than would have been possible when using a strict waterfall approach.
  4. The Spiral Model: It develop software by developing a small prototype (innermost loop of the spiral). This first prototype follows a mini-waterfall process, but is very quickly developed and serves primarily to gather requirements. The last stage of this inner loop is review, or evaluation, of the first prototype. In further loops, we gather further requirements, design, and implementation and review till we get the official release.
  5. Agile Approach: Agile is a software development methodology to build a software incrementally using short iterations of 1 to 4 weeks so that the development process is aligned with the changing business needs. Instead of a single-pass development of 6 to 18 months where all the requirements and risks are predicted upfront, Agile adopts a process of frequent feedback where a workable product is delivered after 1 to 4 week iteration.

Chosen Methodology:

In this application we have followed waterfall methodology. As we already know that waterfall model follows non iterative design process and its design process is sequential. So our application also revolves around these following steps:

  • Conception
  • Initiation
  • Analysis
  • Design
  • Construction
  • Testing
  • Production/implementation
  • Maintenance

Reasons for chosen methodology:

There are multiple reasons for choosing the waterfall methodology:

1-This was an extremely complex project which needed extreme research as there is no such application ever developed in Pakistan. All the steps could not have taken on the same time but it needed sequential design.

2-We have worked on a very complex project so even a minute change could have disturbed all the processes within. This can result in wrong results which can be a disaster for our application.

3- Problems found in early stages are very important for projects like these. A problem found in the early stages (such as requirements specification) is cheaper to fix than the same bug found later on in the process (by a factor of 50 to 200).

4- The waterfall method has save our 10%-20% of our time because after proper research and design the development phase was comfortable to implement.

5-The waterfall model has provided us a structured approach; the model itself progresses linearly through discrete, easily understandable and explainable phases and thus is easy to understand; it has also provided us easily identifiable milestones in the development process.

Drawbacks of other methodologies:

  1. Opportunistic approach does not acknowledge the great importance of working out the requirements and the design before starting implementation.
  2. When following the spiral model, a project undergoes a large number of cycles. The cycling only ends when the system is finally retired.

Phase model continues to suggest that all requirements be finalized at the start of development, and it continues to downplay the possibility of prototyping. The model does not facilitate learning lessons from Phase 1, which could result in improvements to subsequent phases.

Designing the Project


Designing the project requires extreme vigilance as design determines the interface of the project. If the GUI of project is not right no one will even bother to use this application.

We have taken every care to make the design as attractive as possible. First of all the splash screen appears with the name of our application and a logo design. And afterwards a simple interface appears which allows you to take picture. The most important feature of our design is its ease to use.


The purpose of designing the application is to make sure that the user stays on application and feels comfortable. Another purpose of a good design is to assist the developers in development of the application because the right design determines the approach of the developers.


The scope of our application starts from our splash screen so the user comes to know about the application. Then the application opens the camera after which he picture can be captured and the rest of the process is continued

Definitions, acronyms and abbreviations

  • Splash screen:

A splash screen is a graphical control element consisting of a window containing an image, a logo and a current version of the software. A splash screen usually appears while an application is launched.

  • Logo:

Logo is a symbol or other small design adopted by an organization to identify its products, uniform, vehicles, etc.

Logo Diagram

App Logo

App Logo

Architecture Diagram

Architecture Diagram

Architecture Diagram

Sequence Diagram

Sequence Diagram

Sequence Diagram

Class Diagram

Class Diagram

Class Diagram

Deployment Diagram

Deployment Diagram

Deployment Diagram

Data Flow Diagram (Level 0)

Data Flow Diagram (Level 0)

Data Flow Diagram (Level 0)

Data Flow Diagram (Level 1)

Data Flow Diagram (Level 1)

Data Flow Diagram (Level 1)

Data Flow Diagram (Level 2)

Data Flow Diagram (Level 2)

Data Flow Diagram (Level 2)

Activity Diagram

Activity Diagram

Activity Diagram

Graphical User Interface

Graphical User Interface

Graphical User Interface







After gathering all requirements and designing phase, this chapter includes how actually the android application is built. We will introduce modules that we have covered during this phase, which technology we relied on and what ways we went through to develop our robust application.

Technologies used:

We have used android studio to build this powerful and robust application where a user will be able to recognize their note currency through camera phone. Our team has used android open CV library to build this application. Reason why our team selected this library is that it captures clear and sharp images with high pixels and great image quality.

As it will be helpful in detecting note characteristics

Picture Clarity

The images taken from this library camera has high performance and very accurate results. As this is very important in detecting currency notes because of their minor differences in design.

Steps for note detection

Capture Image

The smartphone allows application to capture currency note images through open CV library. When a user opens application, a splash screen occurs and a camera opens in open CV. In this step application takes image and sends request to OpenCV for note detection

Capture Image

Capture Image

Capture Image

Resize & Hist Equalization

Application find the picture on note and send request to OpenCV for resizing and applying histogram equalization (Histogram Equalization is a technique for adjusting image intensities to enhance contrast) .

Note Detection

After the resizing and hist equalization OpenCV match the image with already stored image. If they matched, it is a currency note.

Get RGB Values

User taps on the screen. RGB function takes the RGB values from image at pixel level.

Color Domination

System run the color domination function and find dominant color. values And map those values with the threshold values which are already defined on the basis of currency notes.

Auditory Solution

If dominant color values mapped with already defined values, system provides the auditory solution.



Testing phase defines whether the application works properly or there are some bugs and defects. This is a critical phase which further elaborates if there is any need of further improvement or there is perfection. Although testing phase cannot perfectly defines the defects and issues related to our application but at least it can prevent us from software failure. It gives us an opportunity to criticize or compare the states and behavior of the product against per-defined processes..

We have also tested our application vigorously to make sure that the application works properly to the best of our ability. Professionals have to take every care so the desired product is delivered to the customer according to his needs without any faults or bugs.

Testing android applications is more challenging than testing web application or website on desktop due to several reasons. Some of these reasons are given below:

  • Different range of mobile devices:

There are different screen sizes and hardware configurations like hard keypad, virtual keypad (touch screen) and trackball etc.

  • Wide varieties of mobile devices or companies:

There are wide varieties of companies like HTC, Samsung, Apple and Nokia.

  • Different mobile operating systems:

There are different operating systems like Android, Symbian, Windows, Blackberry and IOS.

  • Different versions of operation system :

There are different versions of operating systems like iOS 5.x, iOS 6.x, BB5.x, BB6.x etc.

  • Different mobile network operators:

Different mobile operators like GSM and CDMA cause another problem.

  • Frequent updates:

Another problem for tester are the frequent updates (like android- 4.2, 4.3, 4.4, iOS-5.x, 6.x) – With each update a new testing cycle is recommended to make sure no application functionality is impacted.

Types of Mobile Testing

There are broadly 2 kinds of testing that take place on mobile devices:

1. Hardware testing:

The device including the internal processors, internal hardware, screen sizes, resolution, space or memory, camera, radio, Bluetooth, WIFI etc. This is sometimes referred to as, simple “Mobile Testing”.

2. Software or Application testing:

In this phase of testing application and its functionality is tested. It is called the “Mobile Application Testing” to differentiate it from the earlier method.

3. Types of Mobile App Testing:

To address all the above technical aspects, the following types of testing are performed on Mobile applications.

Test Plan

In this process, we will design a complete test plan in which we will manage how each process of system will be tested before it is passed to final release.

The Test Plan is derived from the Test Approach, Requirements, Functional Specs, and detailed Design Specs. The Test Plan identifies the details of the test approach, identifying the associated test case areas within the specific product for this release cycle.

The purpose of the Test Plan document is to:

  • Specify the approach that Testing will use to test the product, and the deliverables (extract from the Test Approach).
  • Break the product down into distinct areas and identify features of the product that are to be tested.
  • Specify the procedures to be used for testing sign-off and product release.
  • Indicate the tools used to test the product.
  • List the resource and scheduling plans.
  • Indicate the contact persons responsible for various areas of the project.
  • Identify risks and contingency plans that may impact the testing of the product.
  • Specify bug management procedures for the project.
  • Specify criteria for acceptance of development drops to testing (of builds).

Unit Testing:

While coding, the programmer performs some tests on that unit of program to know if it is error free. Testing is performed under white-box testing approach. Unit testing help developers decide that individual units of the program are working as per requirement and are error free.

It can also be stated as tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors. One unit might have multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify the functionality of a piece of software, but rather is used to assure that the building blocks the software uses work independently of each other.

It also ensures that proper functionality and code coverage have been achieved by each developer both during coding and in preparation for acceptance into iterations testing.

In our system, developer has conducted test driven development approach and utilized unit testing. Each module or unit was tested separately by the developer for example ride posting, ride requesting, registration, and login units etc.

System Testing:

The software is compiled as product and then it is tested as a whole. This can be accomplished using one or more of the following tests:

Functionality Testing -Tests all functionalities of the software against the requirement specified by project stakeholders.

Performance Testing - This test proves how efficient the software is. It tests the effectiveness and average time taken by the software to do desired task. Performance testing is done by means of load testing and stress testing where the software is put under high user and data load under various environment conditions.

Security & Portability - These tests are done when the software is meant to work on various platforms and accessed by number of persons.

Integration Testing:

Even if the units of software are working fine individually, there is a need to find out if the units if integrated together would also work without errors. For example, argument passing and data updating etc.

Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together ("big bang"). Normally the former is considered a better practice since it allows interface issues to be localized more quickly and fixed.

Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

Acceptance Testing:

When the software is ready to hand over to the customer it has to go through last phase of testing where it is tested for user-interaction and response. This is important because even if the software matches all user requirements and if user does not like the way it appears or works, it may be rejected

Alpha testing - The team of developer themselves perform alpha testing by using the system as if it is being used in work environment. They try to find out how user would react to some action in software and how the system should respond to inputs.

Beta testing - After the software is tested internally, it is handed over to the users to use it under their production environment only for testing purpose. This is not as yet the delivered product. Developers expect that users at this stage will bring minute problems, which were skipped to attend.

  • Usability testing:

Usability testing makes sure that the mobile app is easy to use and provides a satisfactory user experience to the customers. Testing of this type was required for our application.

  • Compatibility testing:

We have to make sure that our application is compatible with the mobile devices of our users. Testing of the application in different mobiles devices, browsers, screen sizes and OS versions according to the requirements. Testing of this type was required for our application.

  • Interface testing:

In interface testing we test menu options, buttons, bookmarks, history, settings, and navigation flow of the application. Testing of this type was required for our application.

  • Services testing:

Testing the services of the application online and offline. Testing of this type was not required for our application. Our application works offline and it does not needs internet for working.

  • Low level resource testing:

Testing of memory usage, auto deletion of temporary files, local database growing issues known as low level resource testing. If continues to accumulate more Ram it means there is problem with application which has to be identified.

Testing of this type was required for our application.

  • Performance testing:

Testing the performance of the application by changing the connection from 2G, 3G to WIFI, sharing the documents, battery consumption, etc.

Testing of this type was not required for our application.

  • Operational testing:

Testing of backups and recovery plan if battery goes down, or data loss while upgrading the application from store.

Testing of this type was not required for our application.

  • Installation tests:

Validation of the application by installing /uninstalling it on the devices.

Testing of this type was required for our application.

  • Security Testing:

Testing an application to validate if the information system protects data or not.

Testing of this type was not required for our application.

Test cases and results

Id NumberTest Case NameOwnerStateTest Case descriptionPre-conditionPost-Condition


Splash Screen



Working of Splash screen

Splash screen should show

Passed Test









Camera opening



Camera opening properly

Camera should open properly

Passed Test









Image capturing



Camera is positioning right and working perfectly

Image should be captured properly










Currency Note Detection



Currency notes should be detected

Detecting currency notes










Processing Speed



Processing speed should be minimum

Very fast processing









Conclusion and Future Work


Our current discussion is purely on technical grounds on how we can improve this application. We want to improve its reliability for the users, so these users can efficiently use our application and achieve their desired objective of using this application.

Our focus is not its efficiency and processing time. So its processing time is as low as possible, making sure that the users feel comfortable while using this application.

Future Work:

1-Implement this system in all Pakistan with the help of State Bank of Pakistan:

We want to collaborate with collaborate with state institutions like State Bank of Pakistan to refine this app and make sure that it works professionally. We will also make sure that this app is provided to everyone and an awareness campaign is started all over Pakistan.

2- Detecting the counterfeit currency notes

Counterfeit notes are one of the biggest problem which world is currently facing and this continues to plague the Pakistani society. Its recent example is the Figure 1.1 which is shown below. This is also a problem which common people of Pakistan continue to face. Now consider a point when people would be able to detect fake or counterfeit currency notes using the mobile phone camera. Surely it will be a great day for Pakistan. For this we are working vigorously and want to achieve this milestone as soon as possible.

If we can achieve this future goal surely this application will develop into something sensational which is never heard of.

The picture below is a latest report of how counterfeit currency notes are flowing in Pakistani society.

Surely this day is near when we will continue in our pursuit of robotic eye for visually impaired people using mobile phone camera.

Deployment Plan:

These are the basic steps for publishing our application:

Deployment Plan

Deployment Plan

Details of Publishing the Application on Google play account

Sign up for your Google Play account using this link:


Click All Applications and then click + Add new application.


Select your Default language, enter your app Title and click Upload APK.

Our Default language is English and our application title is Recogo afterwards we will upload the Apk file.


Click Upload your first APK to Production.


Click Browse files, and browse to your .APK file.

See Download Your APK File for more information.


Click the Store Listing tab.


Enter the following product details.


Your app name.

Short description

The initial text users will see when looking at your app’s Store Listing from the Play Store app.

Full description

A description of your app, including its features and what users can do. This description appears on the app store and cannot be longer than 4000 characters.

Store listing


Click + Add Screenshots to add screenshots of your app. Note: You can take a screenshot of your app from the live simulator in the app editor.

We will provide atleast2 screenshots of your app. To have your app displayed in the Designed for tablets section of Google Play, upload tablet screenshots.

Graphic resolutions:

Phone: 320 X 640 Tablets: 1024 X 768 or 1280 X 800


Click + Add high-res icon to add your app icon (must be at least 512 X 512).

  1. Click + Add feature graphic. This is a promotional graphic that's displayed at the top of your Store Listing page in the Play Store app. See Choose a Google Play Feature Image for more information.
  2. (Optional) Add a Promo Graphic to promote your app on older versions of Android and a Promo Video (YouTube video URL) to promote your app. These are optional but should be given.

Select your Application Type, Category, and Content Rating.

Note: Google Play's new content rating system requires you to also fill out a rating questionnaire. For more information, click here.


[1] A comprehensive detail of how to gather functional requirements can be taken from the guidelines mentioned in Object Oriented Software Engineering, written by Timothy C. Lethbridge and Robert Laganiere, PP 120-122

[2] Chapter 1: A detailed view of quality requirement guidelines taken as Non-functional requirements mentioned in Object Oriented Software Engineering, written by Timothy C. Lethbridge and Robert Laganiere, PP 123-124

[3] Use case scenarios and description referred in chapter 1 taken from Object Oriented Software Engineering, written by Timothy C. Lethbridge and Robert Laganiere, PP 129-131

[4] Software process models referred in chapter 2 as Waterfall methodology mentioned in Object Oriented Software Engineering, written by Timothy C. Lethbridge and Robert Laganiere, PP 430-433

[5] UML Diagrams structure and pattern guidelines taken from Applying UML and Patterns, Third Edition published by Addison Wesley Professional in 20th October, 2004

[6] UML design and patterns version 2.2 library included in Microsoft Visio Professional 2013, used as a tool to meet up project design requirements

© 2020 Sumair Sajid

Related Articles