Difference between hosted feature layer vs. feature layer (Visualization > Save As)

[Bud]

I have a hosted feature layer in AGOL:

I can open the layer in the Visualizations tab, change something like the symbology, the pop-up field order, or the form configuration field order. Then Save As.

The new layer is shown in the Contents tab as a feature layer, not as a hosted feature layer.

Questions:

1. What's the difference between a hosted feature layer and a feature layer?
2. Does the feature layer point to the hosted feature layer?
3. Does a feature layer not allow me to set privileges for it?
4. Why would I use a feature layer instead of a view?

[RussRoberts]

Save As is creating a new feature layer item that is using the original hosted service. Its not the original hosted feature layer item so that's why it does not say hosted but if you looked at the layer JSON you will see it just points to the same service as the hosted one but you cannot alter editing functionality, overall sharing level of the original service and more. It is also not a view where a backing view layer has the restricted area of interest, fields and editing configuration. 

[Bud]

@RussRoberts (and @bbollin)

Thanks. What's the benefit of a feature layer compared to a view? On the surface, it seems like a view has more functionality, so why would someone use a feature layer?

[RussRoberts]

Views can only be created by the owner or admin of the layer but the benefit is the various share settings and editing controls that can be configured. On the feature layer item is just an item pointing to the original service that could store any configuration of popups, table, symbols, filter etc. the feature layer item though cannot hide fields, features or change editing configurations. Also if someone changes the sharing the original hosted feature layer to private then the feature layer item that was saved off using the Save As which could be public or org wide shared still is just pointing to the original service referenced in that item is now private. This means that item no longer would work for those org or public viewing users when they load the item in a new map or open an existing map with the non-hosted version of the item. The service will be reported as no longer accessible.