RED SIGNAL 2014 Year in Review

As December is about to become history and New Year is joining us in next week, we wanted to reflect on the achievements, milestones and moments that marked our year. Record growth, exceptional new and existing client initiatives, and our notoriously famous (the world loves when we party) in-house events made for a memorable 2014, and we can’t wait to see what 2015 has in store. Here’s an overview of key moments from the ‘soon to be past year’.

Bigger, Faster, Stronger

2014’s been a great year for us at RED SIGNAL. A lot of stuff happened through us. A lot of new faces joined us. A lot of ideas got realized through us. New technologies and new tools kept reaching us. More than 15 new hires joined our team, bringing us to a super nerd 50+ REDS. Contributing to these impressive figures was the addition of some great partnerships with global clients. We expanded our reach to 75 countries spread across 6 continents.

We lived every single day of this year.

As a direct result of our continued growth throughout the year, we successfully launched 21 new ecommerce sites, 14 enterprise web apps and 21 mobile apps. These comprised both B2B and direct-to-consumer solutions and apps across a range of industries, including some of the largest and most complex implementations we’ve worked on in our born days.

Our clients? They were thrilled to see our work. To give you an idea, here is what they are saying.

Btw, what were we like in 2013?

 

Oh, what’s not been included among our 2014 roster was the redesign of our own website, conceptualized and launched in-house on a responsive framework by our cross-functional delivery team. We’re especially proud of the ‘About Us’ section of the new site, reflecting a great sense of our personality and highlighting our commitment to developing relevant, timely solutions alongside and guided by our expertise.

RED SIGNAL website 2011

Giving Back

2014 made us 10 years old. Wasn’t it the time to give something back to the people living around us. On different occasions of the year, we donated more than 5,000,00 in charities, donations and community support programs. To encourage a more knowledge-oriented society, we launched 3 programs.

www.tuition.com.pk – A state of the art website to connect tutors and students from around the world and help them learn and earn.

www.bathak.com – An entertainment portal for latest news, views, articles, columns, videos and discussions.

www.careerizm.com – An all things HR related portal, bring tips, tricks, tutorials from the best brains of the HR world.
Happy holidays and best wishes for a successful 2015 from all of us at RED SIGNAL!

How much does it cost to develop a web app or application?

So, here you are. Chances are that you must have an idea for a web or mobile application and want to see if it’s something feasible and within your budgets. There is no direct answer to this question. First we need to understand what goes in making an app. So, let’s go through it.

BASICS: Functional specifications or user stories

Any software development project starts with a detailed understanding of what the application does. To understand it we have two different methods.

The first one involves creation of functional specification document. A functional specification document describes the exact behavior of an application, its components and their front/backend functionality. Most enterprise clients we work with prefer this method as it broadly follows a waterfall approach to development, meanwhile allowing us to lock down features and costs (fixed cost/fixed time). The downside? Well, since features/functionality of the project has been locked down, there is no room for changes in it. Any changes in requirements would affect project timelines and eventually the cost.

On the other hand, User Story is the second approach we use for web application development. A user story is one or more sentences to describe what an application or the users are supposed to do. Say, ‘I want a web based application where group of friends can share pictures with each other’. This leads us to ultimate 5Ws: Who, Why, When, Where, What. And How, as well. Agile development methodology comes handy here. Since, when compared with functional specs, user stories are rather flexible and allow continuous improvements/modifications, Agile environment entertains it better where focus is on iterative and incremental development.

Example Agile User Stories

User Story: “As a manager, I want to administer a skills audit so that I can understand the capabilities of my staff.”

STORY TEST CASES
As a manager, I want to browse my existing quizzes so I can recall what I have in place and figure out if I need to update based on the skills my team’s acquiring. Make sure it’s possible to search by quiz name and quiz banks included.
As a manager, I want to browse the quiz banks so I can make sure I’m subscribed to all the necessary topics for my skills audit. Make sure the banks are searchable by topic.
The user can send select a set of quizzes and send an email with a note to the purchasing authority (i.e., “These are the quiz banks we should buy”).
As a manager, I want to purchase additional quiz banks so I can add additional technical topics to my quizzes. The manager is able to purchase additional quiz banks.
If the users don’t have purchase authority, they see a list of those that do.
The charges are correctly prorated against the billing anniversary of the account.
As a manager, I want to create a custom quiz bank so I can add my own questions to the quiz. The customer is not charged for this bank.
The custom bank is invisible to any other accounts on the system.
As a manager, I want to create a quiz so I can use it with my staff. The administrators can set the length of the quiz in terms of number of questions.
The administrators can allocate a set quantity of questions from any of the available quiz banks.
The administrators cannot allocate questions from a quiz bank they are not subscribed to.
If the administrators try to allocate more questions from a bank than remain against the unallocated total questions in the quiz, they will receive a descriptive error that includes total questions in the quiz, questions from each bank so far.
As a manager, I want to create a list of students from an Excel file so I can invite them to take the quiz. The system accepts a standard Excel template we provide.
The Excel template is downloadable from the page where the users go to create the list of students.
If the users upload an invalid file, they receive an error that directs them to the correct template file and warns them not to modify it.
As a manager, I want to create a list of students online. The users can paste in a comma or tab separated list of student emails, and the system will identify the individual email addresses.
The users can create students individually.
The users can specify email addresses and optional names.
As a manager, I want to invite a set of students to take a quiz so I can receive their scores. The users receive a helpful error message if the list of students is blank.
If the email delivery to the students fails, the managers should receive a notice and the failure should be visible on the portal.
The managers see the list of students and must confirm before sending.
As a manager, I want to see which students have completed the quiz and which have not so I can send them a reminder. The users can see a list of students who have competed vs. not completed the quiz.
There is a visual indicator for students whose email invitation failed.
The users can customize the body of said email.
The email sends in under two minutes.
As a manager, I want to see how the students scored on the test so I can put in place a skills improvement program. The users can search by student first name and/or last name.
The users can see a presentation that shows all the students’ scores and the averages.
It is impossible to see any reports if you are not an administrator.

 So, What’s better?

There is no right or wrong answer here. It depends on following things.

  1. You have fixed budget and time-frame with locked-in features?

Yes? Waterfall development model fits your project.

  1. Do you have an idea with features that you might want to change many times throughout the development process?

Yes? Agile gives you opportunity to design, develop, redesign, redevelop your application until you are satisfied. Remember, it’s not going to be fixed price/fixed time model. Such projects involve different engagement models, commonly referred as Time/Material engagement or more popular one, Dedicated team/s.

Looking back at our experience with projects, we have seen that Functional specification (waterfall methodology) best fits enterprise applications development where the requirements are unlikely to change very often. This allows for comprehensive, well planned and well scoped document creation.

Whereas, user stories (Agile methodology) best serve consumer applications development where users’ input/output make up the big chunk of application. These applications, usually need to be extremely flexible and fast. Since it’s not possible to offer fixed price/fixed time for such applications, development team is paid for set amount of time like per hour, week or a month. Clients can ask team to develop any feature or change it altogether later.

At RED SIGNAL, we don’t force these methodologies. We realize that every project is different. Depending upon the nature and scope of the project, we decide which one to use. Sometimes, we use hybrid approach that combines both.

One More Thing, where to find damn good development team?

The best way to find a great fit? Research a few companies who are good at what they are doing, talk to them, see their work and if possible do their clients check. Don’t just go for a guy that offers you the lowest cost. At the end of the day, you would want a team that you can trust. When tried everybody, Call 00923212423100. It’s our Business Director’s number.

Did we forget to mention average cost of application development?

By now, you have got a good idea that every project is different. Having said, on average our team has about 175 billable hours per week for our custom projects and average web/mobile application development project lasts about 3 months and costs in $25,000 to $65,000 range.

Finally,

Soon, we are going to launch our case histories. You bet, you will not have seen anything like this before. Stay InspiRED. Stay Engaged.

Blood, Sweat, and a Great App

We have heard it before: I have an app and I want to get it featured on the App Store. Well, of course having an app featured in App Store is by no means a small feat. But, before that, why not talk about more important thing – Great product

Building a good product and in this case, ‘a great app’ is much more than just good strokes of design and cool taps and gestures. It’s a journey that takes lots of efforts and resources along the way. But finally, this is only the best who will make it to the end: To the Top.

So, what’s a ‘great product’ for users?

UX? You are right. App store is just about to explode any time. Thousands of apps are submitted daily for review. Finding an app from app store is just as difficult as finding needle is from hay. Even if a user downloads your app and launched it, you have only few seconds to impress him. And, remember, there is no 2nd time.

This is where most of the apps fail. Latest Report from Localytics might give you an idea of what we are talking here. It says that 22% of downloaded apps are only used once before being totally abandoned.

Besides, products are meant to solve ‘problems’. Whether this is a fitness tracking app or a feature rich project management app, it’s meant to be ‘only the best’. Most of the apps die their own death because, they never solve the problems, and in some worse case, become another problem. It’s very important to first identify the problem and then rise as a solution for it.

Finally, great products are built upon great design. If there is one advise that we can give you, this is: Hire the most talented, most innovative and most dependable UI/UX designer.

Now, What’s a ‘great product’ for Apple?

Apple is Godfather of modern design. People quote Steve Jobs to impress others and show them how good they are at designing products. Well, Apple takes design very seriously and so should you.

With Apple’s latest update of iOS, standards of design have been changed again. Flat design, translucence and blur effects and dogmatic advocacy for simplicity are new commandments for mobile app development. So, try following Apple’s guidelines and you would have more chances to score better among the competition. By the way, here are the apps that won ‘Apple Design Award’ in 2014.

Apple design awards

Other than latest design trends, Apple highlights those apps as well which are very good with Apple technology. To our clients, we never stop suggesting them to update their mobile apps with latest Oss, than spending time over supporting older versions. So, while working on new mobile apps, try to consider:

  • Build for latest iOS devices. Use hardware APIs like location, Wifi/Bluetooth, accessory kit;
  • Latest SDK features (Game Center, Passbook, Maps etc.)
  • Support latest OS releases and use APIs such as iCloud, AirPlay, AirPrint, notifications, in-app purchases;
  • Build for all users, even with visually/hearing impairments. Add accessibility options like voice over, closed captioning, zoom, mono audio and white on black mode.

Finally, What it takes to design and develop Great App:

Apple tells us what it takes to make a ‘great app’. John Geleynse, Director of Technology Evangelism at Apple talked comprehensively over it. In this short video Ingredients of a Great App”, he defines great app as:

‘Delightful, Innovative, Sate of Art, Connected, Accessible, Localized, Designed and Disruptive’

Our quick thoughts on this subject are:

  • Make your app multi-lingual, when you are going to sell to different countries or worldwide.
  • Free is good, but not always. Apple is much more likely to feature paid apps. No brainer.
  • Update app regularly (fix bugs AT LEAST once in 2 months) to show you are still standing behind your app
  • Get positive reviews. And get lots of them
  • Make it compatible for all Apple devices (where applicable).
  • Innovate and take risks sometimes. (Apple always buys new technologies. Remember Siri?)

You can see how a great app is produced: Mobile Apps Development

At the end, don’t make just another app. If you want to spend money, you have better ways to spend anywhere else. But if you really want to have an app, make sure you have the right idea, right team and right time and then right budget to handle everything. By the way, we are always here to help you with your app ideas!