Project organisation, features ideas and technical questions

joxad commented 4 months ago

Hello guys,

I have a few ideas of features, and one in particular that could help a lot for the contributions.

Project Tracker

I guess you also have some features in mind. Do you have any tracker like trello, or githubproject to have sort of a backlog of what you want to add ?

Features ideas

[ ] Simple account management (possible to use firebase), to store the data of the climber in the cloud instead of the phone. This way, if you uninstall the app, change phone or else, you can keep your climbing history.
[ ] Contribute within the application using the map (I can make a POC of that, without the webservices call). I guess there is an endpoint to make the contribution ?
[ ] Make the sync of the boulders/zones at start of the application instead of being in the app (which needs an update of the app every time someone contributes

Technical questions

For the contribution part, how does it work to push the data ? Is there an API to add new content ?
In the android app, I saw the link to an api, but it seems used only to get the picture?

For a little of background, I used to work 4/5 years ago on a similar project of yours, which is not existing anymore ( except here https://apkcombo.com/fr/beautifulboulders-the-application-of-climbers/novajox.io.beauxbloc/ ) for many reasons. If you're interested I can give you the full story another time :D

In this project, I also used mapbox, with firebase to store the data on the cloud and make the sync at the startup of the app. So I'm so happy someone did what I wanted to do so long ago and make it work, that's really awesome :)

nmondollot commented 4 months ago

Hey,

Thank you for your message!

With @wang-li we're currently discussing the upcoming roadmap, we should have something to share next week hopefully.

Simple account management (possible to use firebase), to store the data of the climber in the cloud instead of the phone. This way, if you uninstall the app, change phone or else, you can keep your climbing history.

Yes that's a great idea, and it's very high in our wish list :) We'll probably use our own Rails backend, though.

Contribute within the application using the map (I can make a POC of that, without the webservices call). I guess there is an endpoint to make the contribution ?

We've only built the website for now, so there's no endpoints. And I'm afraid it's not high on our todo list right now, so the website will have to do for now.

Make the sync of the boulders/zones at start of the application instead of being in the app (which needs an update of the app every time someone contributes

Yes, that's actually a topic we've discussed several times with @wang-li ! We'd love to make updates more seamless (and faster). This may be a complex endeavor hower, with several technical implications. I'd be happy if you or @wang-li worked on a proof-of-concept 👍 But maybe we should get you started on an easier feature? What do you think?

In the android app, I saw the link to an api, but it seems used only to get the picture?

Yes, only the photos for now. We want most of our app to work 100% offline, that's why we use the local database.

We may also use webviews in the future. We want to use our native skills only on screens with high value (lots of UI interactions, offline, used often, etc).

I'll get back to you soon about the roadmap.

Cheers!

joxad commented 4 months ago

Hey

Thanks for the feedbacks ;)

Yes for long term, It will be better to update on the rails part instead of using something like firebase or else. I used it because it was easier for me at this time, but using Boolder own infra, you will handle better what is possible.

For the sync at start up we can discuss if u want :) tell me when!

Yep np for something easy to start with

Cheers

boolder-org / boolder-android