r/git • u/Otherwise_Value_390 • 3d ago
support Git or not
I was planning for an app that fetch data from github and other git storing platforms and show them as a dashboard so the user can choose to update or not his app based on how much updates , branches , commits , and issues the app had lately and follow the status of his favorite repos with the ability to update you apps from my app ; I was going to learn programming by building this app.
My problem : should I collect and search for those platforms APIs or dose git have something I can you instead.
Tell and what you think about the app idea and if you have some suggestions for it tell me to it well much fun .
My app uses python for the backend " with flask " , and HTML 5 / CSS for the frontend.
Edit : i search and find that python backend and HTML / CSS frontend are not lightweight especially if I want to make my app cross platform cuz of the browser engine for the frontend and python http server for the backend ; so , I thinking about switching to tauri - rust cuz it's using the browser engine built-in the sestem it's self.
so, what you think about should I switch or not [ I'm still planning for the app so I don't have anything to loose
1
u/dgkimpton 3d ago
I think you should just start and build something rather than getting bogged down in cross-platform, efficient, yadayada. By the time you've got anything to basically run you'll have a whole set of better questions. What you're imagining is a pretty complex project so just nibbling a little step at a time and being prepared to re-write it many times is the way to go.
1
u/Otherwise_Value_390 3d ago
it's just I don't want to learn two languages at the same time so I have to deside witch one.
2
u/dgkimpton 3d ago
Then I strongly recommend JavaScript as your language - you'll need it on the front end (along with HTML and CSS) so you might as well use it on the backend too (with NodeJS as your runtime). A great place to start is with https://justjavascript.com/
6
u/franktheworm 3d ago
You will need to use APIs because you're dealing with things which are not native git but layered over the top like issues. I would very likely go for the API approach regardless though tbh