Feature Request: Replace CircularProgressIndicator with Spinkit

[RunTerror]

In the provided image, we currently use a circular progress indicator for loading images.
Consider implementing the Spinkit package to showcase a loading animation that aligns seamlessly with the overall theme of our application.

[Dante291]

Hello @RunTerror ,we incorporate new packages into our project only if it's challenging to implement a particular feature using existing packages. This approach ensures security, so loading indicator do the work for now.

[RunTerror]

can we implement a shimmer effect or another animation. The current progress indicator undergoes shape changes, which can appear somewhat unconventional.

[Dante291]

yeah thats a bug need to be fixed you could work on that but i wouldnt suggest adding a whole new package just for this, do ask from @Cioppolo14

[RunTerror]

i have tried to create this animation with code only we are not using any package here.

Screen.Recording.2024-01-20.at.15.43.26.mov

can we implement this in our application directly

[Azad99-9]

@RunTerror I appreciate your effort to contribute to Talawa, please go through this comment before raising any issues.

[Cioppolo14]

@RunTerror Thank you for your submission. I am going to close this issue for now.

We are now focusing on three types of issues as priority areas:

1. The improvement in the reliability of our code base. There are many issues created to test existing code. It is a good place to start if you want to understand the operation of various apps. When you submit PRs, we automatically check to see whether the code you submitted has been covered by testing and that each file meets the minimum standard level of the repository as a whole. You won’t be able to avoid understanding testing regimes to contribute to Talawa.
2. The fixing of bugs and features that seriously hamper the user from using the application. The apps have various shortcomings. The most obvious ones are where the apps do not work as expected. For example buttons that don’t work, errors or messages that are not displayed to make the user understand what to do and many more. Think of any difficulty you have had in getting things working, there could be a bug there waiting for you.
3. Coding of screens for issues created by our Contributor team based on our soon to be updated design guide. This may include updates to existing screens.
4. The creation of additional or updated documentation that helps with improving both the experience of the end user and the various GitHub contributors who support the development of our software. This would include user guides.

We will only be accepting feature issues for deficiencies that are obviously lacking in the apps. These are things that make it very difficult to operate the apps. Even so, the PRs will still require you to understand testing as stated before.

Cosmetic changes that require only a few lines of code are not acceptable under this policy.

Closing