Is it a norm in android apps to only have bottom navigation only on parent activities

I have checked multiple apps, and in most of them, bottom navigation is only visible on parent activities, when i go in any inner activity bottom navigation goes away, so my question is that is there any guideline regarding this available in material design, or everyone is just following this approach without any proper guideline,

and is it a right approach to have bottom navigation only on parent activities.

and in which cases we hide navigation on child activities, if not in all.

For example, i have an item in navigation Team, when user taps on it i open Team Screen, which contains 5 items, so when user further goes into these items i disable navigation, is it the correct approach?

Why does price change in second page in many apps

In food delivery apps and cab aggregator apps there is price difference in India.

In food apps – I add the items from restaurant menu. it shows total of 240 rs. I navigate to place order page. All the additional charges and taxes are shown now.

In cab aggregator apps they show a price in first page and when you chose a particular category or variant and proceed to the second page all the taxes and deposits and other fares get added and price gets inflated.

Isn’t this a dark pattern? As a user I often feel misled and confused with this kind of pricing tactics. Is it just me or anyone else feels the same? So the question is why does the industry practice this? I have some theories, but I am interested in knowing what others think.

For chicken-and-egg apps which require a network effect, should I try to delay my user from noticing early on that there aren’t many others?

For example, in my user registration, I can let the user pick preferences for other users, similar to a dating app.

If those other users get filtered out, this introduces the possibility for the user’s first impression using the app to be, “Oh, there’s nobody here. Is this thing dead?” -> close -> uninstall -> and they’ll probably never come back. Churn. Actually, it’s just brand new!

So while I’m growing the app and there’s not many on it yet, should I leave those preferences out of the registration, just so their first impression isn’t that the app is dead, and slightly delay it, allowing them to choose the preferences later? They could still potentially get value from the app if it’s not just their strict preferences right away.

I know there’s not too much I can do here, but what is your recommendation?

Is Progressive Web Apps accessible only from mobile, how to deploy

Hey guys,

Have you ever heard about Progressive Web Apps? I just hear about it today and I scoured every web corner to understand what it is. The information is so scant.

All I know is it's standalone app on the web and accessible via mobile.

The example of this feature is

It cannot be accessed via desktop. Data on the web seems to fetch instantly once you tap on the link.

Do you have any idea how to they deployed it.


Apps loaded in App Catalog do not have the correct App Version or Product ID

I’m working with a client who just set up a new SharePoint 2016 site on their server. They created an App Catalog but when I load in a custom SharePoint App, the App Catalog doesn’t read in the version from the AppManifest.XML and sets the version to nor is the app assigned a Product ID – the Product ID is left blank.

The same App is uploaded with the correct metadata on other sites.

Is there something that needs to be configured so the App Catalog library behaves like an App Catalog?

Thanks in advance