Add badges when repo is published
Wall@ is an innovative mobile app that revolutionizes the way you scan and manage documents on your smartphone. With our easy-to-use and powerful app, you can easily capture, store, and keep documents like receipts, invoices, IDs, and other important documents at your fingertips.
- Document scanner: Use your smartphone's camera to scan high-quality documents and save them as digital versions.
- Secure digital wallet: Keep your scanned documents safe and organized in one place, always at hand and always accessible.
- Intuitive user interface: A simple and engaging user interface allows for smooth navigation and effortless operation of the app
- Cross-platform compatibility: Wall@ runs seamlessly on iOS and Android devices, providing a consistent user experience across both platforms.
Add current installation instructions here.
We are happy about your feedback! If you have any questions, suggestions or problems, please do not hesitate to contact us.
Find the latest documentation (only availabe in German) here .
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
If you have ideas for releases in the future, it is a good idea to list them in the README.
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Show your appreciation to those who have contributed to the project.
For open source projects, say how it is licensed.
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.