Splash screens (also known as launch screens) provide a simple initial experience while the mobile app loads. They set the stage for the application, while allowing time for the app engine to load and the app to initialize.

Pull requests with adequate descriptions, and context make code easier to review, test, and discuss. Also Having clear and concise templates will improve the process of feature request and bug reports.

Users cant check whether they have entered the correct password or not in the login and signup forum. Toggle password visibility is missing in both signup and login forum.

The existing app icon is the default flutter app icon. It's always better to keep the UI up-to date. And the name of the app is currently not similar to the project name. It's awesome if we can change it to DengueStop

Expected Behavior

The app screen should adapt to different screen sizes and should not return a Bottom overflowed by some number of pixels message with caution tape.

Actual Behavior

Once the user gets into the login screen, it returns the Bottom overflow issue with caution tape.

Screenshots

Error Log at DEBUG CONSOLE

I/flutter ( 2623): ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter ( 2623): The following assertion was thrown during layout:
I/flutter ( 2623): A RenderFlex overflowed by 64 pixels on the bottom.
I/flutter ( 2623): The relevant error-causing widget was:
I/flutter ( 2623):   Column 
lib\views\login.dart:176
I/flutter ( 2623): The overflowing RenderFlex has an orientation of Axis.vertical.
I/flutter ( 2623): The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and
I/flutter ( 2623): black striped pattern. This is usually caused by the contents being too big for the RenderFlex.
I/flutter ( 2623): Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the
I/flutter ( 2623): RenderFlex to fit within the available space instead of being sized to their natural size.
I/flutter ( 2623): This is considered an error condition because it indicates that there is content that cannot be
I/flutter ( 2623): seen. If the content is legitimately bigger than the available space, consider clipping it with a
I/flutter ( 2623): ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex,
I/flutter ( 2623): like a ListView.
I/flutter ( 2623): The specific RenderFlex in question is: RenderFlex#7ca1f relayoutBoundary=up3 OVERFLOWING:
I/flutter ( 2623):   needs compositing
I/flutter ( 2623):   creator: Column ← _FormScope ← WillPopScope ← Form-[LabeledGlobalKey<FormState>#f4224] ← Padding ←
I/flutter ( 2623):     DecoratedBox ← Container ← LoginForm ← Expanded ← Column ← Semantics ← DefaultTextStyle ← ⋯
I/flutter ( 2623):   parentData: offset=Offset(8.0, 8.0) (can use size)
I/flutter ( 2623):   constraints: BoxConstraints(0.0<=w<=304.0, h=380.8)
I/flutter ( 2623):   size: Size(304.0, 380.8)
I/flutter ( 2623):   direction: vertical
I/flutter ( 2623):   mainAxisAlignment: start
I/flutter ( 2623):   mainAxisSize: max
I/flutter ( 2623):   crossAxisAlignment: center
I/flutter ( 2623):   verticalDirection: down
I/flutter ( 2623): ◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤
I/flutter ( 2623): ════════════════════════════════════════════════════════════════════════════════════════════════════

Steps to Reproduce the Problem

1. get into dengue_app folder

  cd dengue_app

2. run the flutter app

  flutter run

Testing Specifications

• Version: Flutter 1.12.13+hotfix.8
• Platform: Android 7.0 Nouget ( API level 25 )
• Device: Sony Xperia Z5 Compact

This issue relates to front-end and back-end implementation of the component which is used to view the incidents reported by a particular user.

The finished UI should correspond to this design

I installed the project and there is an issue, the * key is not working in the app. Also Where is the community chat room?

Hey
I am a GSOC 2k21 aspirant and wanted to contribute to your community. I found this dengue stop application quite useful and solving major issues in countries. I have an idea regarding this application:- why not take this application to android and mobile so that it has a better reach and in place of using it specifically for dengue we can use it for many other pandemics and diseases that are spreading in today's world. Being an android developer I could surely work upon this idea if the mentors allow me.

Please find the detailed project plan here.

Milestone 1

• Setting up the new project and initial configurations. (Mobile App)

• Designing the database structure.

• Creating the database and the server using Flask.

• Setting up end-points to be consumed by the mobile application.

• Incident reporting and viewing feature. (Mobile App)

• User registration and authentication. (Mobile App)

• User profile viewing and editing feature. (Mobile App)

• Implementing events feature - front-end (Mobile App)

• Setting up the new project and initial configurations. (Web App)

• Testing for milestone 1.

• Documentation for milestone 1.

Milestone 2

• Code refactor after milestone 1.

• Dashboard Component - Heatmap (Web App)

• Dashboard Component - Incident receiving feature (Web App)

• Dashboard Component - Incident verification feature (Web App)

• Dashboard Component - Incident summary feature (Web App)

• Patient/Incident List Component - Incident view feature (Web App)

• Patient/Incident List Component - Incident searching feature (Web App)

• Patient/Incident List Component - Incident filtering/sorting feature(Web App)

• Metrics Component - Chart visualization (Web App)

• Metrics Component - Metrics logic (Web App)

• Testing for milestone 2.

• Documentation for milestone 2.

Milestone 3

• Code refactor after milestone 2.

• User registration and authentication. (Web App)

• Alerts/Events sending feature. (Web App)

• Implementing events feature - back-end (Mobile App)

• Testing for milestone 3.

• Documentation for milestone 3.

• Finalizing the project.

There's a bug in the reported incident screen which raises when we change the province dropdown when the district dropdown is already selected and contains data.