Make Zappiti work without Internet Connection/Cloud server
Due to problems with the cloud server by Zappiti, the unit does not function anymore. All files are on local storage, but because of outage on the zappiti cloud server the zappity does not work!!!. This is very bad!!!
Make it to also work without a internet connection.
The problem is that Zappiti sells hardware. This material once bought we keep it for years (and that's normal). How do you want this business model to be profitable to also develop a free interface + cloud storage. I proposed to Zappiti to start on a paid model for the use of the interface which for a small fee (example 30 € per year) would allow them to hire a team of developers and put the user experience at the heart of the interface. It really feels like guys work in a garage with 2-3 people. They certainly do the maximum but it is clearly not enough to ensure development
Joe Lie commented
If you struggle to make Zappiti work without an internet connection or cloud server, consider seeking assistance from a reliable Java coursework service. With their programming and software development expertise, they can provide you with the necessary support to ensure that Zappiti works smoothly and efficiently offline. By relying on a trusted Java coursework service, you can save time and avoid the frustration of troubleshooting the issue independently.
Visit us at: https://reportwritinghelp.com/coursework/java-coursework-help/.
Mikael Bäckstedt commented
It has now been in R&D for over 4 months. Any progress?
Jauschua Stout commented
The best solution is to run Zappiti Server on your local network. You can do this in several ways. Zappiti has official downloads for several platforms. By doing this, your metadata is local and it does not require a connection to the Cloud. If Zappiti does not have an official download, check out https://hub.docker.com/r/theimmortal/zappiti-server, which allows you to run Zappiti Server in a docker container.
When will this finally be implemented. ???
The solution for now is NOT A SOLUTION.
Making a backup cost 3 hours and every time the application jumps into screen saving and stopped the backup process.
So you have to be on the watch for 3 hours. Every time you make a backup.
The problem is Zappiti don't understand that end user internet connections aren't reliable. Their excuses online with the recent outage were that cloud issues like the one experienced aren't common. They forget their end users all sit behind individual internet connections, not a global cloud service.
Just goes to show you how disengaged they are from the end user experience. They should have kept the functionality years ago instead of stripping it out as they do with countless useful features for seemingly no reason at all. They need a new Product Manager.
You can should make the Zappitis save cloud content once a week automatically and you do your updates the day after…
This is so bad. How can zappiti deliver such a poor service!
Mikael Bäckstedt commented
Keep a local primary database on the Zappiti hardware itself and then SYNC to cloud (secondary database). How this isn't default behaviour is beyond me...
This would increase performance as well as reliability!
Also, this idea has been suggested before, but DECLINED by Zappiti. Seriously, what are you thinking?