Or, download the standard PDF template.
Freelance android app design is one of the fastest growing work segments out there today.
Over 1 billion Android devices were shipped in 2014, giving it 81 percent of the worldwide market. By comparison, Apple only has 15 percent of the worldwide market. There are over 1.6 million apps in the Google Play store, which is also more than in the iOS app store.
A variety of factors drive freelance android app design demand. The biggest one is that apps are seen as a new way to grab market share by everyone from Fortune 500 companies to small businesses to entrepreneurs. Indeed, Android is the fourth most searched term on the popular job search site Indeed.
Because there's such a need for freelance android app designers, it's critical that freelance designers use a solid Android contract when working with new or returning clients. Having an Android contract will help set the proper expectations about exactly what work will be done, when it will be done by, and what will be paid for it. These are some of the most common and most painful issues that come up between clients and the freelance android app developers that they hire.
Even if you’re working with a long-term client, you still need to draft a contract every time they hire you. Not that they’re not trustworthy, but you need to keep it professional. While a client knows that they need to make payments on time and provide the necessary tools to get the job done, they may not live up to this. If you’re working without an android contract template, you’ll find it challenging to cope with a client at this point. You may be forced to either accept things as they are or get into unhealthy arguments. As a freelancer, that’s the last experience you’d like to have with a client, especially if you’re working hard to build a strong reputation.
Consider using an Android app design contract template for you to avoid such issues that arise in the course of work. Usually, this document defines the terms of work and payment so that both the client and freelancer know what’s expected of them at a particular time. For instance, based on the payment timeline indicated in the android contract template, a client will ensure a freelance app designer gets their dues on time. And for you as a freelancer, it’s your duty to provide all the services within your scope of work without fail. That’s a fair deal, and, therefore, none of you will have something to complain about in the end.
If you’re a newbie in the freelance business, you may be wondering what makes a good android app design contract template. We have several contract samples online, so you can always go through them and find out more. Nevertheless, a standard android contract template should contain the essential features that a typical freelance contract has.
We recommend that freelance android app design contracts cover three main clauses. First, these Android contracts should cover the scope of work, i.e., exactly what the freelancer will be designing for the client. This is one of the most most common sources of conflict between freelancers and their clients. Will the freelancer be responsible for designing the android app, or also developing it? How high fidelity do the designs need to be? Freelancers should also be clear in the contract about what designs will be provided to the designer by the client, versus what the designer will need to find or create.
Android app development is quite involving, and you’d like to get paid for every service you offer. While the client knows this, you may end up providing services beyond your scope of work. Therefore, to be on the safe side, you need to clearly define your scope of work in the android contract template. Sometimes, a client may request for extra services, which you may want them to pay for. Since you’ve been on the job long enough, you can highlight these extra tasks on the android app design contract template.
Also, don’t forget to mention how much they would cost. Most clients don’t take it kindly when you talk about charges outside the contract. So it’s important to keep them in the know before you start working on the project. As you do this, remember that the scope of work should be in line with the goals and objectives of the project at hand.
The second important clause to have in your Android contract is the payment information. As a freelancer, you’re working on a client’s project to receive payment on completing the tasks. You’d like the client to pay all your dues on time. The client knows this too, and they’ve it in mind. However, it’s necessary to include your payment terms in the android app design contract template. In that way, you’ll not have to disagree with your client during payment. A good android contract template should answer the following questions:
It’s up to the freelancer to let the client know how much they would like to receive at the end of the project. For instance, if you’re working on milestones, you should clearly state the amount you wish to be paid after completing the given portion. Also, don’t forget to talk about the timeline to avoid late payment.
2. How will the client pay you after signing the Android app design contract template?
It’s essential to talk about the mode of payment in the android app design contract template. To make it easier for both you and the client, go for a payment method that’s widely used. You can also discuss with your client to know their preference.
As a freelancer, you wouldn’t want to get to this point with a client. However, some clients tend to be stubborn, and they may not be ready to pay you after completing the tasks. It’s challenging to deal with such clients, but with an android contract template, the problem is half solved.
These are all terms that are very important to you!
The last important clause is to be very clear about intellectual property ownership after the Android app design is complete. This should only transfer over to the client once they have paid all their invoices. However, you should be careful to note whether the client only owns the final product or all sketches, designs, and ideas that went into the Android app. In most cases, clients and freelancers disagree over copyright ownership.
Therefore, even before you start working on a client’s project, be sure to discuss it with them. Most clients would like to have complete ownership of the final product, which is just fine. But make sure they pay for it.
Every freelancer needs to work a contract to get the most out of their business. As an android app designer, get the best android app design contract template to get started.
This Contract is between Sample Client (the "Client") and John Doe (the "Developer").
The Contract is dated [the date both parties sign].
1. WORK AND PAYMENT.
1.1 Project. The Client is hiring the Developer to do the following: The Designer will assist the Client with app design services.
1.2 Schedule. The Developer will begin work on August 21, 2020 and the work is ongoing. This Contract can be ended by either Client or Developer at any time, pursuant to the terms of Section 6, Term and Termination.
1.3 Payment. The Client will pay the Developer a rate of $90.00 (USD) per hour. Of this, the Client will pay the Developer $600.00 (USD) before work begins.
1.4 Expenses. The Client will reimburse the Developer's expenses. Expenses do not need to be pre-approved by the Client.
1.5 Invoices. The Developer will invoice the Client weekly. The Client agrees to pay the amount owed within 15 days of receiving the invoice. Payment after that date will incur a late fee of 5.0% per month on the outstanding amount.
1.6 Support. The Developer will not provide support for any deliverable once the Client accepts it, unless otherwise agreed in writing.
2. OWNERSHIP AND LICENSES.
2.1 Client Owns All Work Product. As part of this job, the Developer is creating “work product” for the Client. To avoid confusion, work product is the finished product, as well as drafts, notes, materials, mockups, hardware, designs, inventions, patents, code, and anything else that the Developer works on—that is, conceives, creates, designs, develops, invents, works on, or reduces to practice—as part of this project, whether before the date of this Contract or after. The Developer hereby gives the Client this work product once the Client pays for it in full. This means the Developer is giving the Client all of its rights, titles, and interests in and to the work product (including intellectual property rights), and the Client will be the sole owner of it. The Client can use the work product however it wants or it can decide not to use the work product at all. The Client, for example, can modify, destroy, or sell it, as it sees fit.
2.2 Developer’s Use Of Work Product. Once the Developer gives the work product to the Client, the Developer does not have any rights to it, except those that the Client explicitly gives the Developer here. The Client gives the Developer permission to use the work product as part of the Developer's portfolio and websites, in galleries, and in other media, so long as it is to showcase the Developer's work and not for any other purpose. The Developer is not allowed to sell or otherwise use the work product to make money or for any other commercial use. The Client is not allowed to take back this license, even after the Contract ends.
2.3 Developer’s Help Securing Ownership. In the future, the Client may need the Developer’s help to show that the Client owns the work product or to complete the transfer. The Developer agrees to help with that. For example, the Developer may have to sign a patent application. The Client will pay any required expenses for this. If the Client can’t find the Developer, the Developer agrees that the Client can act on the Developer’s behalf to accomplish the same thing. The following language gives the Client that right: if the Client can’t find the Developer after spending reasonable effort trying to do so, the Developer hereby irrevocably designates and appoints the Client as the Developer’s agent and attorney-in-fact, which appointment is coupled with an interest, to act for the Developer and on the Developer’s behalf to execute, verify, and file the required documents and to take any other legal action to accomplish the purposes of paragraph 2.1 (Client Owns All Work Product).
2.4 Developer’s IP That Is Not Work Product. During the course of this project, the Developer might use intellectual property that the Developer owns or has licensed from a third party, but that does not qualify as “work product.” This is called “background IP.” Possible examples of background IP are pre-existing code, type fonts, properly-licensed stock photos, and web application tools. The Developer is not giving the Client this background IP. But, as part of the Contract, the Developer is giving the Client a right to use and license (with the right to sublicense) the background IP to develop, market, sell, and support the Client’s products and services. The Client may use this background IP worldwide and free of charge, but it cannot transfer its rights to the background IP (except as allowed in Section 11.1 (Assignment)). The Client cannot sell or license the background IP separately from its products or services. The Developer cannot take back this grant, and this grant does not end when the Contract is over.
2.5 Developer’s Right To Use Client IP. The Developer may need to use the Client’s intellectual property to do its job. For example, if the Client is hiring the Developer to build a website, the Developer may have to use the Client’s logo. The Client agrees to let the Developer use the Client’s intellectual property and other intellectual property that the Client controls to the extent reasonably necessary to do the Developer’s job. Beyond that, the Client is not giving the Developer any intellectual property rights, unless specifically stated otherwise in this Contract.
3. COMPETITIVE ENGAGEMENTS. The Developer won’t work for a competitor of the Client until this Contract ends. To avoid confusion, a competitor is any third party that develops, manufactures, promotes, sells, licenses, distributes, or provides products or services that are substantially similar to the Client’s products or services. A competitor is also a third party that plans to do any of those things. The one exception to this restriction is if the Developer asks for permission beforehand and the Client agrees to it in writing. If the Developer uses employees or subcontractors, the Developer must make sure they follow the obligations in this paragraph, as well.
4. NON-SOLICITATION. Until this Contract ends, the Developer won’t: (a) encourage Client employees or service providers to stop working for the Client; (b) encourage Client customers or clients to stop doing business with the Client; or (c) hire anyone who worked for the Client over the 12-month period before the Contract ended. The one exception is if the Developer puts out a general ad and someone who happened to work for the Client responds. In that case, the Developer may hire that candidate. The Developer promises that it won’t do anything in this paragraph on behalf of itself or a third party.
5.1 Overview. This section contains important promises between the parties.
5.2 Authority To Sign. Each party promises to the other party that it has the authority to enter into this Contract and to perform all of its obligations under this Contract.
5.3 Developer Has Right To Give Client Work Product. The Developer promises that it owns the work product, that the Developer is able to give the work product to the Client, and that no other party will claim that it owns the work product. If the Developer uses employees or subcontractors, the Developer also promises that these employees and subcontractors have signed contracts with the Developer giving the Developer any rights that the employees or subcontractors have related to the Developer’s background IP and work product.
5.4 Developer Will Comply With Laws. The Developer promises that the manner it does this job, its work product, and any background IP it uses comply with applicable U.S. and foreign laws and regulations.
5.5 Work Product Does Not Infringe. The Developer promises that its work product does not and will not infringe on someone else’s intellectual property rights, that the Developer has the right to let the Client use the background IP, and that this Contract does not and will not violate any contract that the Developer has entered into or will enter into with someone else.
5.6 Client Will Review Work. The Client promises to review the work product, to be reasonably available to the Developer if the Developer has questions regarding this project, and to provide timely feedback and decisions.
5.7 Client-Supplied Material Does Not Infringe. If the Client provides the Developer with material to incorporate into the work product, the Client promises that this material does not infringe on someone else’s intellectual property rights.
6. TERM AND TERMINATION. This Contract is ongoing, until ended by the Client or the Developer. Either party may end this Contract for any reason by sending an email or letter to the other party, informing the recipient that the sender is ending the Contract and that the Contract will end in 7 days. The Contract officially ends once that time has passed. The party that is ending the Contract must provide notice by taking the steps explained in Section 11.4. The Developer must immediately stop working as soon as it receives this notice, unless the notice says otherwise. The Client will pay the Developer for the work done up until when the Contract ends and will reimburse the Developer for any agreed-upon, non-cancellable expenses. The following sections don’t end even after the Contract ends: 2 (Ownership and Licenses); 3 (Competitive Engagements); 4 (Non-Solicitation); 5 (Representations); 8 (Confidential Information); 9 (Limitation of Liability); 10 (Indemnity); and 11 (General).
7. INDEPENDENT CONTRACTOR. The Client is hiring the Developer as an independent contractor. The following statements accurately reflect their relationship:
- The Developer will use its own equipment, tools, and material to do the work.- The Client will not control how the job is performed on a day-to-day basis. Rather, the Developer is responsible for determining when, where, and how it will carry out the work.- The Client will not provide the Developer with any training.- The Client and the Developer do not have a partnership or employer-employee relationship.- The Developer cannot enter into contracts, make promises, or act on behalf of the Client.- The Developer is not entitled to the Client’s benefits (e.g., group insurance, retirement benefits, retirement plans, vacation days).- The Developer is responsible for its own taxes.- The Client will not withhold social security and Medicare taxes or make payments for disability insurance, unemployment insurance, or workers compensation for the Developer or any of the Developer’s employees or subcontractors.
8. CONFIDENTIAL INFORMATION.
8.1 Overview. This Contract imposes special restrictions on how the Client and the Developer must handle confidential information. These obligations are explained in this section.
8.2 The Client’s Confidential Information. While working for the Client, the Developer may come across, or be given, Client information that is confidential. This is information like customer lists, business strategies, research & development notes, statistics about a website, and other information that is private. The Developer promises to treat this information as if it is the Developer’s own confidential information. The Developer may use this information to do its job under this Contract, but not for anything else. For example, if the Client lets the Developer use a customer list to send out a newsletter, the Developer cannot use those email addresses for any other purpose. The one exception to this is if the Client gives the Developer written permission to use the information for another purpose, the Developer may use the information for that purpose, as well. When this Contract ends, the Developer must give back or destroy all confidential information, and confirm that it has done so. The Developer promises that it will not share confidential information with a third party, unless the Client gives the Developer written permission first. The Developer must continue to follow these obligations, even after the Contract ends. The Developer’s responsibilities only stop if the Developer can show any of the following: (i) that the information was already public when the Developer came across it; (ii) the information became public after the Developer came across it, but not because of anything the Developer did or didn’t do; (iii) the Developer already knew the information when the Developer came across it and the Developer didn’t have any obligation to keep it secret; (iv) a third party provided the Developer with the information without requiring that the Developer keep it a secret; or (v) the Developer created the information on its own, without using anything belonging to the Client.
8.3 Third-Party Confidential Information. It’s possible the Client and the Developer each have access to confidential information that belongs to third parties. The Client and the Developer each promise that it will not share with the other party confidential information that belongs to third parties, unless it is allowed to do so. If the Client or the Developer is allowed to share confidential information with the other party and does so, the sharing party promises to tell the other party in writing of any special restrictions regarding that information.
9. LIMITATION OF LIABILITY. Neither party is liable for breach-of-contract damages that the breaching party could not reasonably have foreseen when it entered this Contract.
10.1 Overview. This section transfers certain risks between the parties if a third party sues or goes after the Client or the Developer or both. For example, if the Client gets sued for something that the Developer did, then the Developer may promise to come to the Client’s defense or to reimburse the Client for any losses.
10.2 Client Indemnity. In this Contract, the Developer agrees to indemnify the Client (and its affiliates and its and their directors, officers, employees, and agents) from and against all liabilities, losses, damages, and expenses (including reasonable attorneys’ fees) related to a third-party claim or proceeding arising out of: (i) the work the Developer has done under this Contract; (ii) a breach by the Developer of its obligations under this Contract; or (iii) a breach by the Developer of the promises it is making in Section 5 (Representations).
10.3 Developer Indemnity. In this Contract, the Client agrees to indemnify the Developer (and its affiliates and its and their directors, officers, employees, and agents) from and against liabilities, losses, damages, and expenses (including reasonable attorneys’ fees) related to a third-party claim or proceeding arising out of a breach by the Client of its obligations under this Contract.
11.1 Assignment. This Contract applies only to the Client and the Developer. The Developer cannot assign its rights or delegate its obligations under this Contract to a third-party (other than by will or intestate), without first receiving the Client’s written permission. In contrast, the Client may assign its rights and delegate its obligations under this Contract without the Developer’s permission. This is necessary in case, for example, another Client buys out the Client or if the Client decides to sell the work product that results from this Contract.
11.2 Arbitration. As the exclusive means of initiating adversarial proceedings to resolve any dispute arising under this Contract, a party may demand that the dispute be resolved by arbitration administered by the American Arbitration Association in accordance with its commercial arbitration rules.
11.3 Modification; Waiver. To change anything in this Contract, the Client and the Developer must agree to that change in writing and sign a document showing their contract. Neither party can waive its rights under this Contract or release the other party from its obligations under this Contract, unless the waiving party acknowledges it is doing so in writing and signs a document that says so.
(a) Over the course of this Contract, one party may need to send a notice to the other party. For the notice to be valid, it must be in writing and delivered in one of the following ways: personal delivery, email, or certified or registered mail (postage prepaid, return receipt requested). The notice must be delivered to the party’s address listed at the end of this Contract or to another address that the party has provided in writing as an appropriate address to receive notice.
(b) The timing of when a notice is received can be very important. To avoid confusion, a valid notice is considered received as follows: (i) if delivered personally, it is considered received immediately; (ii) if delivered by email, it is considered received upon acknowledgement of receipt; (iii) if delivered by registered or certified mail (postage prepaid, return receipt requested), it is considered received upon receipt as indicated by the date on the signed receipt. If a party refuses to accept notice or if notice cannot be delivered because of a change in address for which no notice was given, then it is considered received when the notice is rejected or unable to be delivered. If the notice is received after 5:00pm on a business day at the location specified in the address for that party, or on a day that is not a business day, then the notice is considered received at 9:00am on the next business day.
11.5 Severability. This section deals with what happens if a portion of the Contract is found to be unenforceable. If that’s the case, the unenforceable portion will be changed to the minimum extent necessary to make it enforceable, unless that change is not permitted by law, in which case the portion will be disregarded. If any portion of the Contract is changed or disregarded because it is unenforceable, the rest of the Contract is still enforceable.
11.6 Signatures. The Client and the Developer must sign this document using Bonsai’s e-signing system. These electronic signatures count as originals for all purposes.
11.7 Governing Law. The laws of the state of California govern the rights and obligations of the Client and the Developer under this Contract, without regard to conflict of law principles of that state.
11.8 Entire Contract. This Contract represents the parties’ final and complete understanding of this job and the subject matter discussed in this Contract. This Contract supersedes all other contracts (both written and oral) between the parties.
All our templates are legally vetted, and can be signed electronically.
Or, download the non-editable PDF version.
1. Follow our step by step editing process to add your own terms to this template
2. Review & sign the contract, then send it out to be electronically signed.
3. Sit back and enjoy the time & money you just saved