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

Mobile browsing should be kept out of the scope of this application #142

Closed
benel opened this issue Dec 6, 2023 · 1 comment
Closed

Comments

@benel
Copy link
Member

benel commented Dec 6, 2023

As the mobile features were diverging from the desktop features, it appeared that it was harder and harder to keep them in the same code base.
If the need for mobile browsing emerges again, a distinct application should be developed.

All the related tickets (#63, #64, #108, #117, #126, #137) will then be copied in the new repository.

benel added a commit that referenced this issue Jan 7, 2024
As mobile browsing was developed, especially for self-guided tours, 
it appears that the mobile interface differed more and more from the
desktop one.
Keeping both in the same codebase made the resulting code too complex.
For this reason, the corresponding features (#94, #93 and #99) are now
removed from this application but could be put together in the future 
as a distinct frontend (with the same backend).
@benel
Copy link
Member Author

benel commented Jan 7, 2024

Closed by f094507.

@benel benel closed this as completed Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant