Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proof Of Concept for potential winds.mobi web client replacement #14

Open
4 tasks
MichalBryxi opened this issue Aug 27, 2024 · 1 comment
Open
4 tasks

Comments

@MichalBryxi
Copy link

MichalBryxi commented Aug 27, 2024

As per following line in the README:

If you would like to share your own version that will eventually replace this client, please open an issue that presents your project.

I started tinkering around to see how hard would it be to have somewhat functional parity to the winds-mobi-client-js. It does not seem like a completely ridiculous idea wrt/ scope or time investment. I should have couple of fairly capable people willing to invest their resources into this.

Currently the app is only able to:

  1. Query the API for current state of the weather stations and display heaps of them over Interlaken
  2. Gain users GPS location and re-center
  3. Have some niceties wrt/ PWAs and mobile version

Demo

The app is now deployed on https://winds-mobi-client-web.netlify.app/ and updates with each merge to main.

Screenshots

Screen.Recording.2024-09-04.at.08.57.47.mov

Open questions

PWA / mobile native?

I personally prefer to have web (PWA) version as opposed to native apps, but I've heard people would nowadays rather have native experience. I believe all the functionality we'd need is achievable from PWA and it's less code to maintain (iOS, Android AND web). And if needed, we can make a native wrapper and bundle it as an app either way?

  • Is it a good direction to build a PWA?

Official cooperation?

Would it be ok to think about an official cooperation by eventually using the official project (sub)domain? Thinking about https://new.winds.mobi. With possibility to eventually replace https://winds.mobi if the project is successful?

  • Use winds.mobi subdomain for hosting?
  • Eventually replace "old" winds.mobi app?

Sponsoring?

I would think that the intention of winds.mobi is to stay as commercially independent as possible and love the fact that it's been true. But I talked about few people interested in future development and wanted to ask if backlink to GitHub sponsors / Patreon / whatever would be a no-no or we could figure something out? Obviously with a split to the original team.

  • Sustainable development possibility?
@MichalBryxi
Copy link
Author

Humble ping. I'm now trying to see if I will get the resources (read: time) to work on this. And although having a frontend running parallel to the official winds.mobi is technically possible, it would be good to know if there is +1 or -1 for those efforts from the official winds.mobi team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant