francesco-buscicchio / ecogram

Hello! I am Francesco Buscicchio 🖖

I'm a developer with over two years of experience in the automotive sector. During my career I have worked with several frameworks including WPF and Angular, and I have specialised in C#, Javascript, SQL and Typescript languages.

In addition, outside of my job, I have developed several personal projects. My main project at the moment is 🌱🌍EcoGram🌍🌱 (developed in Flutter) , a social network focused on saving the planet. Users are invited to actively participate in specific tasks to unlock additional features of the application and obtain rewards. ♻️

I am always looking for new projects to develop and new technologies to learn. 👨‍💻
I am passionate about technology and want to continue to improve my skills as a developer. 🔝

ecogram's Issues

User Post Interface Not Yet Implemented on Homepage

Issue Description:
The graphical interface for displaying user posts on the homepage has not been implemented yet, resulting in a lack of user-generated content visibility. Currently, the homepage does not have a dedicated section or design to showcase user posts, hindering user engagement and content consumption.

Steps to Reproduce:

Log in to the application using valid credentials.
Navigate to the homepage where user posts should be displayed.
Observe that no section or interface exists to showcase user-generated content.
Current Behavior:

The homepage does not include a designated area or interface to display user posts.
Users are unable to create or view posts from the homepage, limiting interaction and content discovery opportunities.
Expected Behavior:

Implement an intuitive and visually appealing interface for displaying user posts on the homepage.
Create a dedicated section where users can view and interact with posts from other users.
Enable users to create and publish posts directly from the homepage, fostering user engagement and content sharing.
Impact:
The absence of a user post interface on the homepage hampers user engagement and restricts the platform's ability to showcase user-generated content. Users may feel less motivated to contribute or explore content, leading to decreased platform activity and overall user satisfaction. Implementing the user post interface will enhance the platform's functionality, encourage content creation, and promote a sense of community among users.

Attachments:
If applicable, include mockups or wireframes demonstrating the proposed design and layout of the user post interface on the homepage. This will help provide a visual representation of the intended implementation.

Need to create a collection every time a user registers

When a user registers you have to create a collection where they are present:

• UID (String)
• Username (String)
• Mail (String)
• PhoneNumber (String)
• RegisteredAt (Date)

The UID field, must be filled with the UID of the user
The username field must be filled with everything before the "@" in the mail address
The Mail field, with the user's email
The RegisteredAt field, with the date on which the registration is made

Improve navigation bar display

Make it so that when the tab is selected the color of the text changes from black to white and that the whole navigation bar tab is colored and not just the icon

We need to define the structure of firebase

To establish a solid foundation for the EcoGram backend, we need to define the structure of Firebase. This includes determining the organization of collections, documents, and fields within the Firebase database.

Tasks to be completed:

Analyze the data requirements of EcoGram, including user profiles, posts, rewards, and other relevant entities.
Design the structure of collections and subcollections within Firebase, ensuring efficient data retrieval and scalability.
Define the fields and data types for each document, considering the necessary information to support the desired app features.
Establish relationships between different collections, if applicable, to enable seamless data querying and retrieval.
Document the Firebase structure, including collection and document names, field definitions, and any relevant guidelines for future development.
This issue serves as a starting point for establishing a well-structured Firebase backend for EcoGram. Contributors with expertise in database design and Firebase are encouraged to collaborate and contribute to this task.

Please note that no changes to the Firebase structure have been made yet. We value community input and suggestions in defining the most effective Firebase structure for supporting the EcoGram application.

Feel free to share ideas, propose potential structures, and discuss best practices in the comments section. Let's work together to create a robust and scalable Firebase backend for EcoGram!

Need to remove the keys of public

As reported by a Reddit comment we should remove public key display from firebase_option. Instead of hardcoding the API keys in the firebase_options.dart file, we need to create a separate file (e.g. .env) or configure environment variables on the respective production server.

The login page does not have the ability to perform password recovery

Need to develop both front-end (which is similar to login and sign-in interfaces) and back-end

Profile User Data - Binding

Now that the first part of the user's page has been pushed, we need to make sure that that data is taken from firebase and put into the user's inference

Fix Android Compilation

As reported by @jibranabsarulislam in issue #5 when trying to compile for android the project would go to error

Have to implement in the try-catches the error message dialogs

In lib\components\messages there are errorMessage and successMessage. You have to put the errorMessage in the try-catches. For example in the login.

You can find an example in lib\Screens\ForgottenPassword\components\body.dart