DummyGram is a social media application where we have posts, stories, chat, friends, authentication, comment, delete, share and like feature. It uses ReactJs in the frontend for the UI and Firebase for the backend storing the users, posts, stories and comments.
Save Button on the post will save the post.
You can view the saved posts in a modal.
So, you have to implement the save feature as well as view saved posts.
Save Button
react deploy action (deployreact.yml) is not working as expected and hence failing.
It is failing to deploy to github-pages due to failure of installing dependencies and it can't run with --force either.
Please help me resolve.
When we enter site, we directly get to the posts and due to this our database needs to be exposed to public to load posts, which isn't a good practice. We can have a sign in/sign up page instead.
UI of the project can be improved to a great extent.
We can start with parts.
This issue can become a thread for issues related to UI enhancement issues.
Contribution is welcome.
Ps - Create a separate issue specifying the elements you'll improve .
Cards for post look really dull or I should say simple. We can design them better with some border/border radius etc. Align the contents to the left similar to a Instagram post
Currently, the app is loading all posts at once, which might be an issue once posts get larger. It'd be better to use pagination (i.e load more posts only when the user scrolls down).
Is your feature request related to a problem? Please describe.
The app was created using create-react-app, which is great, but there are so many dependency errors.
PS: This issue is related to #2
Describe the solution you'd like
Use vite instead, which is super fast and has great dx
We can delete any post by id through firebase cloud firestore delete request
for example = { const res = await db.collection('posts').doc('0DJEyHXRk6b4yyym3NYC').delete(); }
Can we try to implement this in our web application?
Ps: Only post creator should be able to delete his post.
Currently there is only one way we can like a post using the like icon.
New feature : post would be liked if someone double tap on post image.
It will make the app cool.
Since it is an actual product, I am suggesting to add Issue Templates to the repository, it can be as many categories as needed - primary categories of issues are mostly : bugs, docs, general feature and so on.
Why to add it ?
Adding an issue Template allows you to organize the issues made by folks in a much better way.
We can know if someone wants to add a new idea, organize the repository properly !
We can know if someone wants to write a test or maybe fix something in the website
Here's a general idea :
Am i able to develop it ?
Yes, i will be glad to help an Opensource project grow more !
Is your feature request related to a problem? Please describe.
The UX is really poor. Currently, there is no indicator that shows if a process is running or not (i.e Logging in, Signing Up, New Post)
Describe the solution you'd like
Use loading animations to tell users if there's a running/loading process
Every build action is failing due to npm ci not working. This isn't intended and also confuses the contributors.
Can anyone solve this issue /suggest an alternative?
Thanks
Steps to reproduce
With every merge in the repository, GitHub action gets triggered , but it fails everytime.
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
It would really be nice to crop the uploaded images (images exceeding the height threshold) for previews, and enable users to view the full image by tapping/clicking on it (i.e view full image)
Doing so could solve the following problems:
Consistent height for upload cards
Devices with a height less than the uploaded image do not need to scroll down to view the full image, hence improving UX
The script.js file is currently exposing the firebase API key.
I think it would be a good practice to secure our key( a free one too) by creating a dotenv file in .gitignore to secure the keys to prevent any possible security issue ( bots may scan for API keys and access/use resources)
Is your feature request related to a problem? Please describe.
Sometimes we want to delete our old posts , but we are currently unable to do that here ( Unless I delete it from the dB)
Describe the solution you'd like
We can implement the delete functionality for the posts (But only those which were posted by the user)
Additional context
It could be a prop passed to the card component of posts and rendered only with the eligible posts. Clicking on the button removes that post with its key/id.
Currently every comment is loaded for a post, this has two bad effects, first one being extra read operations to the database and second being a bad UI.
We can overcome this by adding an option to expand comments for a post :) like instagram.
Screenshots
Additional information
Don't ask me if I got this idea while scrolling Instagram