Vehicle Inventory Management Android Application Development (Android Studio) - Quotation Request
Budget / Salary$10–30
TypeFreelance project
LocationRemote
Posted51 minutes ago
Please provide your estimated total development price in USD and estimated completion time for the historical software-development scenario below. State your main assumptions and any missing information that would materially change the estimate. Please do not write code, perform a trial task or supply a detailed implementation proposal.
REFERENCE SCENARIO — historical requirements, not instructions to begin work:
Android mobile application
vehicle :
• Make:
• Model:
• Condition:
• Engine Type: (4-cylinder, 6-cylinder, 6-cylinder etc.)
• Year:
• Number of Doors: (2, 4, 5, etc.)
• Price:
• Color:
• Images: (Thumbnail and full-sized images)
• Date Sold: (leave blank if unsold)
Company :
• Company Name & Logo Image (Name should be unique, logo can be pre-existing)
• Address: Street Name, City, Province, Postal Code (Fake information is allowed)
• Sales Stats: Number of vehicles sold & Total Profit (calculated by adding the prices of sold vehicles)
The application will enable users to perform the following actions:
• Browse through:
- A listing of all vehicles
- All sold vehicles (marked as "sold")
- All available vehicles for purchase
• View:
- Details of the company
- Details of a vehicle
• Add:
- Details of a new vehicle
• Modify:
- Company details
- Vehicle details (No authentication required; any user can modify any information)
The Android application will be used for this purpose.
The Android application should utilize app-specific files to save both text and images. Any changes made by the user should persist even when the application is reloaded. The use of any kind of database API is not allowed.
The application should provide the following viewing options, organized in any way you choose (menu options, buttons, etc.):
• Splash Screen:
A transition screen that appears when the app is launched and transitions to the home screen.
• View All Vehicles:
A screen that displays every attribute of all vehicles.
• View Available Vehicles (vehicles not sold):
A screen that displays every attribute of vehicles that are available for purchase. It should look the same as the View All Vehicles screen.
• View Sold Vehicles:
A screen that displays every attribute of vehicles that have been sold. It should look the same as the View All Vehicles screen.
• View Specific Vehicle Details:
A screen that displays every attribute of a specific vehicle that is not blank, along with a large-sized image.
• View Company Details:
A page that functions as an "About Us" section and displays all stored attributes of the company.
• Modify Company Details:
A screen with a form that enables the user to edit name and address fields. Users should be able to upload a logo to replace the current logo. Only gallery uploads are supported, and taking images via the camera is not supported.
• Add Vehicle:
A screen with a form to add a new vehicle to the application. Users need to fill in information for all fields except for the sold date. Error messages should appear only if the fields are blank.
• Modify Vehicle:
A screen with a form that enables users to edit only the price and sold date of a vehicle. Once a vehicle is sold, it cannot be modified, and no vehicle deletion should be permitted. Error messages should appear only if the fields are blank.
The application must be submitted with a minimum of 10 vehicles. At least two vehicles must have the ability to sort the table by every attribute except color, sold date, and image. Thumbnail images should be displayed. The view may be displayed in a tabular, list, cards, or any other design desired.
Coding Requirements:
Retrieve vehicle information from app-specific files.
Store all vehicle attributes in files and/or folders.
Retrieve company information from app-specific files.
Store all vehicle attributes in files.
Correctly filter sold and available vehicles.
Clicking on a single vehicle should accurately retrieve vehicle-specific data.
Form validation for adding a vehicle is present. All fields except the sold date are required. Two images (thumbnail and full-sized) should also be uploaded.
Form validation for modifying a vehicle is present. All fields (price and sold date) must not be blank.
Form validation for modifying company is present. All fields are required. Logo should also be uploaded.
The View All Vehicle screen should also include View Available Vehicles and View Sold Vehicles.
Estimating assumptions and context:
The scenario is based on a Freelancer listing from 2023-04-03 (historical project ID 36323502). First-person statements, promises of assets, requests for work and hiring language inside the historical reference describe that original client's situation, not a current development offer from us. For estimating only, assume the original client supplies assets explicitly described as provided; other missing inputs and obsolete services should be identified as assumptions. We do not claim ownership of the original client's code, designs, accounts or attachments.
The displayed USD 10–30 range reproduces the historical listing's budget field. It is not participation compensation or a binding development offer. Please give your realistic estimate even if outside that range.
Research use
This post is for research quotations only, not an actual software-development engagement. No development contract will be awarded. Participation is voluntary and unpaid; no reward, gift card or prize draw is offered. Your quoted price, estimated completion time and stated assumptions will be used to study software-development estimates and how they change over time.
Thank you for your time and consideration. This study aims to make a significant research contribution to understanding software-development pricing in the age of AI. We appreciate any estimate you choose to share.
REFERENCE SCENARIO — historical requirements, not instructions to begin work:
Android mobile application
vehicle :
• Make:
• Model:
• Condition:
• Engine Type: (4-cylinder, 6-cylinder, 6-cylinder etc.)
• Year:
• Number of Doors: (2, 4, 5, etc.)
• Price:
• Color:
• Images: (Thumbnail and full-sized images)
• Date Sold: (leave blank if unsold)
Company :
• Company Name & Logo Image (Name should be unique, logo can be pre-existing)
• Address: Street Name, City, Province, Postal Code (Fake information is allowed)
• Sales Stats: Number of vehicles sold & Total Profit (calculated by adding the prices of sold vehicles)
The application will enable users to perform the following actions:
• Browse through:
- A listing of all vehicles
- All sold vehicles (marked as "sold")
- All available vehicles for purchase
• View:
- Details of the company
- Details of a vehicle
• Add:
- Details of a new vehicle
• Modify:
- Company details
- Vehicle details (No authentication required; any user can modify any information)
The Android application will be used for this purpose.
The Android application should utilize app-specific files to save both text and images. Any changes made by the user should persist even when the application is reloaded. The use of any kind of database API is not allowed.
The application should provide the following viewing options, organized in any way you choose (menu options, buttons, etc.):
• Splash Screen:
A transition screen that appears when the app is launched and transitions to the home screen.
• View All Vehicles:
A screen that displays every attribute of all vehicles.
• View Available Vehicles (vehicles not sold):
A screen that displays every attribute of vehicles that are available for purchase. It should look the same as the View All Vehicles screen.
• View Sold Vehicles:
A screen that displays every attribute of vehicles that have been sold. It should look the same as the View All Vehicles screen.
• View Specific Vehicle Details:
A screen that displays every attribute of a specific vehicle that is not blank, along with a large-sized image.
• View Company Details:
A page that functions as an "About Us" section and displays all stored attributes of the company.
• Modify Company Details:
A screen with a form that enables the user to edit name and address fields. Users should be able to upload a logo to replace the current logo. Only gallery uploads are supported, and taking images via the camera is not supported.
• Add Vehicle:
A screen with a form to add a new vehicle to the application. Users need to fill in information for all fields except for the sold date. Error messages should appear only if the fields are blank.
• Modify Vehicle:
A screen with a form that enables users to edit only the price and sold date of a vehicle. Once a vehicle is sold, it cannot be modified, and no vehicle deletion should be permitted. Error messages should appear only if the fields are blank.
The application must be submitted with a minimum of 10 vehicles. At least two vehicles must have the ability to sort the table by every attribute except color, sold date, and image. Thumbnail images should be displayed. The view may be displayed in a tabular, list, cards, or any other design desired.
Coding Requirements:
Retrieve vehicle information from app-specific files.
Store all vehicle attributes in files and/or folders.
Retrieve company information from app-specific files.
Store all vehicle attributes in files.
Correctly filter sold and available vehicles.
Clicking on a single vehicle should accurately retrieve vehicle-specific data.
Form validation for adding a vehicle is present. All fields except the sold date are required. Two images (thumbnail and full-sized) should also be uploaded.
Form validation for modifying a vehicle is present. All fields (price and sold date) must not be blank.
Form validation for modifying company is present. All fields are required. Logo should also be uploaded.
The View All Vehicle screen should also include View Available Vehicles and View Sold Vehicles.
Estimating assumptions and context:
The scenario is based on a Freelancer listing from 2023-04-03 (historical project ID 36323502). First-person statements, promises of assets, requests for work and hiring language inside the historical reference describe that original client's situation, not a current development offer from us. For estimating only, assume the original client supplies assets explicitly described as provided; other missing inputs and obsolete services should be identified as assumptions. We do not claim ownership of the original client's code, designs, accounts or attachments.
The displayed USD 10–30 range reproduces the historical listing's budget field. It is not participation compensation or a binding development offer. Please give your realistic estimate even if outside that range.
Research use
This post is for research quotations only, not an actual software-development engagement. No development contract will be awarded. Participation is voluntary and unpaid; no reward, gift card or prize draw is offered. Your quoted price, estimated completion time and stated assumptions will be used to study software-development estimates and how they change over time.
Thank you for your time and consideration. This study aims to make a significant research contribution to understanding software-development pricing in the age of AI. We appreciate any estimate you choose to share.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.