Good design thinking: possibility of contacting UI/UX designers and using community feedback to create new app designs: Key elements we should use and not forget during development Similar or common issues are being raised increasingly in the Extractor repo, so these questions could be considered for the Extractor too.
#NEWPIPE GITHUB CODE#
strange issues between new and old code.migrate the existing codebase of the app:.See the related Project and also take a look at the plans we have for the current app below. As a first step, please join the IRC from the ReadMe.īy the way, don't worry, all currently open PRs that introduce big features will be merged in NewPipe 0.26.0 or future releases of the current app.
#NEWPIPE GITHUB ANDROID#
We all know how fantastic walls of text are at putting us off from reading, and we'd like to avoid that.Īlso, if you are experienced in Android mobile development and would like to help us out with the rewrite, be sure to reach out to us! We will be using the most modern components whenever possible, as detailed below, so it is sure going to be a good learning experience for everyone involved. Also, if you don't have any directly helpful advice, please, please restrict yourself to just upvoting or leaving a thumbs up instead of commenting, so that there is less noise and more info in the thread. Do we just dump the old code into maintenance mode and start afresh? Or replace it piece by piece like the Ship of Theseus? A combination of the two? Or something else entirely? We believe NewPipe really has the potential to be a staple app in people's devices, if only we could get across this massive hurdle and come out the other side relatively intact. But we can't decide on the approach to get there.Īnyone who's been in the FOSS community for long has come across at least one or two failed rewrites or refactors, and we don't want to repeat such tragic history.
#NEWPIPE GITHUB PROFESSIONAL#
We're very sure the old code needs to go, no matter what, to be replaced by a modern and professional codebase. So, we've discussed and discussed this ad nauseam. We need to migrate to Material Design 3, Kotlin and Jetpack Compose, and unfortunately doing so basically requires rewriting everything. We tried again and again to debug the problems, without luck.Īt the moment NewPipe is relying on libraries and components that have become outdated, which might not only drive users away from the app, but also push away developers wanting to get some experience on new technologies. Although now the code is a bit better, new crashes and unwanted behaviors have arisen, because the interaction between the old and the new code is not optimal. Take for example the player, which has often been deemed " a hot pile of garbage": it underwent a couple major Pull Requests that restructured it while maintaining all features. To mitigate the issues we initially tried to do incremental refactors of various components.
Often users requested features that would make sense, but nobody had the time (and, sometimes, knowledge of the codebase) to implement them. Progress has been slow, since developers were focused on fixing nasty bugs.
It has gotten to the point that we're having difficulties even maintaining the current code and fixing bugs, let alone adding new features, due to complex interconnections and lack of proper modularity. It's been over 7 years since then, and the age of the codebase is starting to show through spaghetti code, outdated UI, bad design choices and instability. The thing is, NewPipe was started, like so many others in FOSS, as an enthusiast project. You might have noticed the somewhat slower and haphazard updates to NewPipe for the last few releases.
0 kommentar(er)
