Boil an egg app - step by step (step 1 - planning)

-
     In this tutorial , I will demonstrate how I built the app, from the design, to the logic and the code itself. 
 
This app was written for educational purposes and is free do download on the market at : 
Boil An Egg  - for devices with API 1.6 and above.
 
unnamed
So what's the deal with this app?
 
it's main goal is to provide users with an easy and useful tool to boil an egg, sounds funny and a bit redundant, but for me it's actually a real need, for I'm known to make boiled eggs which are too soft, or on the other hand -too hard.
so I thought to myself that there's must be an app on the play store which will enable me to time the eggs so they'll be perfect each time.
 
After searching the market and installing couple of apps I found that they are too complicated for my needs so I decided to write an app for my own.
 
1. name for the app: simple is good – “Boil An Egg” 
    package name: because I work at Sela group, I wanted to   
    leverage this app for educational purposes so I used
    com.selagroup.boilanegg
 
2. basic detailed design"
    I wanted to include basic functionality, so it will have a choice between 3 egg sizes(small,   
    medium, large) and 2 egg types (soft,hard). Having this configuration I needed 3X2 lengths
    of cook times. so with some small calculations I figured:
final static int boilTimeHardLargeEgg = 600000; // 10 minutes
final static int boilTimeSoftLargeEgg = 300000; // 5 minutes
final static int boilTimeSoftMediumEgg = 200000; // 4 minutes
final static int boilTimeHardMediumEgg = 500000; // 9 minutes
final static int boilTimeSoftSmallEgg = 100000; // 1.5 minutes
final static int boilTimeHardSmallEgg = 250000; // 4+ minutes
many other apps offer some nifty calculations (egg temperature, humidity..GPS..) but I needed to keep it simple.
 
so the flow I went for has 3 simple steps – all happen in a single activity :
 
1. choose egg size
2. choose egg type
3. hit the start timer button
 
from now on, a timer will countdown until the eggs are ready and cooked, followed by a sound playing which lets the user know that his eggs are ready.
 
sounds simple right?
well, it is
 
once you plan a project and keep it simple, it works. of course that complicated projects should work as well, but for this impromptu app which was written in less than two hours give or take, it should suffice
 
in the next post, I’ll show the code used in the app, and how I planned it out, also it will display some nifty visual effects using gradients for a slick looking GUI.











Comments

Post a Comment

Popular posts from this blog

Spinner VS AutoCompleteTextView

-
Image
       We’ve all been in a situation where we needed to show a list of some sort, a list which should be triggered by a user interaction (click, tap, etc..) A list is simple enough, probably even a spinner if we don’t want to spend that much screen real-estate on showing a list which the user clicks once and probably doesn’t need to see it after that. A spinner can be a real bug once there are too much entries for the user to choose from, how much is too much? that’s a good question – probably it differs from user to user, and probably this will have some performance issues with areal large number of entries, you cannot scroll forever to find what you’re looking for. A simple solutions for the problems mentioned above is an AutoCompleteTextView. it’s a control which is basically a combination of a TextView, EditText, and a Spinner all wrapped up in a single easy to use and configurable control. let’s see how it’s done:   first, in the layout file, c...
Read more

Utilizing Http response cache

-
     A typical mobile application will probably consume some resources from a web server using http requests. This repeated task has some drawbacks: Bandwidth has a cost, polling the same data over and over again results in a waste of user’s quota. the responsiveness and user experience is compromised once the user keeps waiting for data. If the requested data hasn’t changed on the server, then there’s no reason for us to fetch it. Of course, local caching of data is a must, but we also need to be able to refresh the data if it has changed on the server. A simple solution which comes out of the box for API 4+ is http response caching. Http response caching is a mechanism which enables us as developers to save a footprint of the response utilizing the abilities of the Http protocol. Basically, is holds a simple cache of the response which can be defined and enabled in code, and it prevents from fetching unchanged data from the server which was already fetched a...
Read more

ORM for android

-
     ORM – Object relational mapping has been around for quite some time now. Basically it’s a piece of software (regardless of targeted platform), which simplifies the connection between objects (as in OOP) and data in database (mostly used is tables based relational database), and it exists in order to help simplify bridging the gap between the two in our development process.     Microsoft's Entity framework is a great example for a robust easy to use framework which allows creating and querying the database from an object’s point of view with classic object oriented programming paradigms while maintaining all DB construction’s needs such as relationships between objects (tables) such as one to many or many to many including all the indexing, optimization etc..      In android, we have SQLite as a database platform, from simple to advanced application, it’s likely to assume that we’ll need some relational database to store and r...
Read more