Dover Delivery: Prototype android application for sending and receiving orders in a collaborative way

(English) Using lean startup process, the application was developed as part of obtaining credits in master's course at the Federal University of São Carlos UFSCAR Application for transporting products between defined points that defines an alternative mode of transport orders and pave income opportunity to those who want to carry orders. In partnership with Felipe Ugliara (fellipe.a.u@gmail.com )

Idea

• Application for the transport of orders between points defined with competitive value for those who send and opportunity of income for those who transport.
• Alternative mode to the transport of orders, with different deadlines and values. Opportunity to rent to those who want to transport parcels.

What was developed

Using metodologies Lean and Kaizend, the application was developed in 3 iterations (MVPs) containing the following functionalities:

• MVP 1 Application register, User invitation, Route search and schedule, Track shipment of orders, User qualification.

• MVP 2 Delivery models, Pictures on delivery and withdrawal, Register in the application using Facebook.

• MVP 3 Search radius of people on the map, Product detail record, Invitation to use the application via Facebook, Send notifications by email.

Source Code

Front-end: Android application Back-End: .Net based on Azure cloud services

Presentation

• Pdf com a apresentação do MVP1: Planning and Validation, Questionnaire and Results, Business Model Canvas and android application screens

• Pdf com a apresentação do MVP2 e MVP3: Kaizen improvement, Canvas Software, Business Canvas Model, Screens of the android application

Methodology

The methodology used for the development of the application was based on the Startup Kaizen (continuous improvement), object of study from Nathalia Novaes Leonessa (www.startupsorocaba.com.br)

The Startup Kaizen methodology consisted of four phases at each iteration (MVP's):

• Requirements:
  • What is the MVP? How to Validate? What is the business value? Customers? How to make money?
  • Groming, User Stories Survey + key moments = People
• Validation:
  • Which stories have been validated?
  • What impact on the customer?
  • Development prioritization
• Project:
  • How will stories be developed?
  • What are the key activities, resources and partnerships of your startup?
• Implementation:
  • How many bugs were found?
  • How many stories have been tested?
  • How many bugs have been fixed?

Uses aspects of different methodologies

• Business Model Canvas
• Software Canvas
• Design Thinking
• Design Sprint
• Scrum
• Lean Startup

Technologies, languages and tools involved

• Microsfot Azure Services
• Microsoft Visual Studio
• SQL Database
• .Net Framework
• Android Studio
• Google Maps API
• C# Programming Language
• Java Language
• Bitbucket repository
• Rest, Json, Entity Framework, Linq

Copyright

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.