Working with an application developer or an application agency is no different from any vendor, retailer or contractor. You must be constantly reminded fairly to complete the work on schedule, with the right quality.
At Savvy Apps, we often encounter situations such as whether the application has obviously been wronged or simply cannot be completed, but someone still works with the app 's developer forever. Here are 10 signs you should consider when encountering situations like this.
Do not set up the process
When working with an application developer, you will want a clear process, starting with a number of exchanges in a way that understands the situation. This initial process will include strategy, UX and visual design, ensuring everyone understands the identity and behavior of the final product. A programmer who can't do this is like building a house without drawing or designing a living room without considering the design style.
Refer to the following link for the application building process: http://savvyapps.com/blog/app-store-submission-checklist
Do not communicate regularly
You should always talk to your dev app, even daily interaction in the beginning of forming a partner relationship. As mentioned in the process, it's time for the team to make the app look at everything related to the application . You will set up a general strategy and schedule, as well as shorten the set of features and functions … of the app.
When the plan becomes tougher, more robust, the intensity of the exchange will be slightly reduced, but still kept at a constant level. Savvy Apps recognizes between projects, meetings every week will bring good results. If the programmer does not see you constantly, there is a risk that you will get a completely different application than what you want.
Do not track activities
Mobile dev should record the notes in the meeting, summarize the conversation and all important activities. This document ensures that everyone understands what is being discussed and the decisions made like deadlines of work …
Do not request superior suggestions
Your developer may be a programming expert, but that doesn't mean you don't have any important information to share with them. The mentality of Savvy Apps is that you are an expert when it comes to industry and customers for the application you are programming. That knowledge, along with the experience of making apps, will help your product achieve success.
When the process goes in the right direction, the dev app must constantly create opportunities for you to comment on editing, completing the app . Of course, due to programming costs, you also want to comment on the developers. Similar to buying a car, you may not understand exactly how the engine works, but you can support choosing the type of engine you want as well as choosing the color and accessories of that vehicle. .
Processes, communication and feedback are all important signs, but if you have never seen your app firsthand, it's a virtual project. No matter how different the scope of the app is, in general, in the first 2-4 weeks of working with a developer, considering the app's features, there won't be much to show. However, usually at the end of the first month, programmers can demo at least some existing points and some rough features in the application.
By the 2nd month, you should receive weekly programming volume, monitor the features progressively and improve. After the first version of the application is released, you will continue to monitor the bug fix progress, complete the add-on features and other updates.
Application not related to the scope of work
When you regularly receive an application installation, it is possible that the application is close to meeting your requirements. As mentioned, completing a long-term strategy and plan will pave the way for application programming and design. You can review the original document and plan to make sure the developer is building the app in accordance with what was proposed.
In addition, successive mistakes in functionality, delays or too many bugs in the app are signs that you may be hiring an unqualified app dev.
No commitment with deadlines
The app must outline the schedule, the time of completion as well as the date of completion of the overall goal. This is especially important for those who are trying to launch an app with a major event (like a conference) or who want to be the first to enter the market. Usually, it will take 4-6 months to make the app and during that time, there will be some small milestones that need to be completed.
If dev often misses deadlines, high probability will not be able to meet the final finishing date. Deadlines and delays and delayed launch dates will cost you a lot of money. Of course, depending on the complexity of the application, dev won't be able to give you an exact date soon, but after 2-3 months, dev must definitely commit to deadlines more clearly.
Do not work with intellectual property
All things like documents, design drawings, code lines themselves are your intellectual property. When you do not work with those objects, you are making yourself difficult and making the relationship with the programmer worsen. Developers can be the keepers of these documents to make you pay more or to maintain the relationship, especially when the partnership is no longer effective.
At Savvy Apps, we ensure the ability to access real-time to all IPs through various tools like Dropbox, GitHub, Trello and Pivotal Tracker.
Lack of professionalism
Lack of professionalism is not just about a programmer coming to a meeting with a messy, messy hair. It is also that the programmer comes to the meeting without preparing anything, does not see what your application is and generally has an attitude that is too comfortable for you. Most likely, the person is not completely interested in the product.
Everything from process, communication, feedback to demo progress shows a high level of professionalism. Whether dev is passionate about the idea of making apps as much as you do, they still have to take the time to turn the app into a great product.
No connection at the "human" level
At the same time, professionalism doesn't mean becoming a robot. It is still possible to communicate separately with application developers as common interests, cultural sympathies (sometimes this is difficult for offshore developers), solving problems together or simply is that you like to talk to your developer. This connection will go long.
If you want to fire a programmer, there is a risk that your application will have a malicious problem or even a legal dispute. If you still retain the programmer, you will spend money and time, especially the whole project may be difficult with an application developer working poorly.
History is the best guide for the future. Some people still stick with the current situation, convinced that there will be changes in the future. If you are having problems with some or all of these problems, then the problems may not be solved by you immediately.