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

Feat(adev): faster initial loading + iPad availability of the playground #55768

Open
mauriziocescon opened this issue May 12, 2024 · 1 comment
Labels
area: adev Angular.dev documentation area: docs-infra Angular.dev application and infrastructure P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Milestone

Comments

@mauriziocescon
Copy link

mauriziocescon commented May 12, 2024

Describe the problem that you experienced

I’m currently trying to play with angular on my iPad during a short vacation. Unfortunately, I can’t cause "the environment is not supported"… on the other hand, I’m totally capable of doing it with Svelte / Vue / Solid.

I must admit the overall experience of Svelte / Vue / Solid playgrounds on an iPad is quite amazing! 😅

I guess there’s some room for improvements for adev: initial loading performance and iPad (tables) support for occasional usage.

IMG_0066

Enter the URL of the topic with the problem

https://angular.dev/playground

Describe what you were looking for in the documentation

No response

Describe the actions that led you to experience the problem

No response

Describe what you want to experience that would fix the problem

No response

Add a screenshot if that helps illustrate the problem

No response

If this problem caused an exception or error, please paste it here

No response

If the problem is browser-specific, please specify the device, OS, browser, and version

No response

Provide any additional information here in as much as detail as you can

No response

@atscott atscott added the area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) label May 13, 2024
@ngbot ngbot bot added this to the needsTriage milestone May 13, 2024
@atscott atscott added area: adev Angular.dev documentation area: docs-infra Angular.dev application and infrastructure and removed area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) labels May 13, 2024
@bencodezen bencodezen added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label May 20, 2024
@ngbot ngbot bot modified the milestones: needsTriage, Backlog May 20, 2024
@mauriziocescon
Copy link
Author

mauriziocescon commented May 28, 2024

Some other feedback comparing ng-playground with the playground available for other frameworks (solid, vue, svelte). Note: I perfectly understand the current WebContainer limitations, but my feedback is mostly functional.

  1. The accessibility of adev-playground from mobile devices (I tested iPhone / iPad) can be very handy in some cases or for some specific categories of users. In particular:

    • teens / education: for teens or in the education sector, it's quite common to find tablets as devices to access internet. In such cases, users can play with the other frameworks, but not with angular.
    • social media sharing: not uncommon to share links to playgrounds... and not uncommon to quickly check them using mobile devices. Again: angular is out.
  2. I think the default access to ng-playground (template: Minigame) is overwhelming: IMO it passes the message angular is complicated. There's too much complicated code (imagine: teens, but also react developers curious about the latest changes in angular). I'd personally set the default template to Hello world or something simple. Moreover, I think having the template_id reference in the url might help a lot (target: social media sharing).

My 2 cents!

FYI @twerske - @mgechev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: adev Angular.dev documentation area: docs-infra Angular.dev application and infrastructure P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

3 participants