– Footer showing first when Blazor web application loads

I have a Blazor .net core hosted application. When the site runs, the footer shows for a few seconds while the app does authorizing. Is there any way to show a loading indicator whenever there is some activity running? I am specifically referring to when the app is authorizing. I want the contents to load before showing the footer? Please see screenshot.

enter image description here

Any cheapest server for host Asp.Net c# web application and SQL database?

Is there any cheapest server or hosting website for host ASP.NET C# Web application with SQL database

android – 3-tier architecture diagram for e-commerce mobile application

I am working on a 3-tier architecture diagram for an e-commerce mobile application, mainly an Android application.

Since I come from a strong technical background with little to no experience in design or documentation, I am not sure if the diagram and explanation includes all that it should and if it is structured properly with components positioned in their right layer.

This is what I came up with after some knowledge gathering and research:

enter image description here

Presentation Layer:

Components – Screens,Forms, Buttons, Notifications etc..

Presentation Logic – UI specific for different screen sizes, form factors, language and region specific UI/Theme etc..

User Interactions – Text input, buttons click, permissions, enable GPS etc..

Business Layer:

Application Facade – Rest APIs, database APIs

Components – ViewModels that do the validation, helper classes to parse and cleanup the data

Entities – Data models like User, Product, Order, PaymentDetails etc..

Workflow – Data flow between the Entities, like adding a product to cart, checking out a cart etc..

Data Access Layer:

Local Database – SQLite to show data when the application is not connected to internet

Persistent Storage – File storage for any image caching, User preferences etc..

Server Database – Remote database and file system which is used by the Rest APIs


Security – Secure communication between the layers like database encryption, secure payment, HTTPS protocol etc..

Operational Management – Logging Analytics, crash reports etc..

Communication – Interfaces to update the UI, sync the database, send/receive notifications etc..

I would like to know if I am missing anything fundamental or if there are any structural flaws in the diagram. Thanks!

What is the relationship between screen size and application design? Is it a two-way street?

I read this recent article (link not provided since it felt a bit like an ad) on The Verge about the trend of looking beyond 16:9 aspect ratio screen displays, at least according to what is on show at CES.

It makes me wonder what the exact relationship is between screen size and aspect ratio, and the way that apps are designed. Is the app design influencing the screen size and aspect ratio more than the hardware is dictating what the interface looks like?

If we remember back to when the particular release of the iPhone that introduced the ‘notch’ and how designers were frantically scrambling to come up with the right layout to work with this ‘enhancement’ (even if it is just ignoring it all together and moving the interface down a fraction), it would seem like for certain types of devices the relationship is one-way.

However, I tend to think that the article suggests at least for desktops the hardware is limiting the way applications are designed and laid out these days, so the laptops are starting to move away from wide screen designs that don’t seem to offer much improvement or is limiting to how application interfaces can be designed.

Does anyone else have any insights into this? Whether it is some formal research or just anecdotal evidence that there is some relationship of whether software design dictates hardware specifications or vice versa (or if it is even balanced in most contexts).

mysql – Anonymous and Public User Table Design in twitter like application

I have schema design problem which I am not 100% sure if my assumptions are correct.

So the requirements are:

  1. I need to have 2 different type of user, anonymous and public.
  2. A user can have both anonymous and public profile.
  3. A public and anonymous user can follow anonymous and public.
  4. Anonymous user and public user must not be identifiable by clients. Which means if I know public user I shouldn’t be able to fetch anonymous profile details vice versa.

I first come up with idea:

User (id, anon_id,public_id)
Tweet(id, author_id(FK-User),text)

In this design I could split users into two. However, if we know the tweet’s author id we are not able to understand if it’s send by public or anonymous account. And also the same problem exist in Relationship too, we are not able to understand if follower/following is anonymous or public. The solution might be adding 2 more fields to Relation clarify follower/following type ie. follower_type/following_type and 1 more field to Tweet author_type.

Another solution which I felt more correct is


In this design I can have both anonymous and public profiles in same table. And records would look like:

id nickname fullname phone is_phone_registered public
123 slayer John Doe +1 90 123 123 12 12 true NULL
312 vendetta NULL NULL false 123

And public field should not be visible to clients so I am pretty much achieving my goals on security side of things.

Sorry for my ignorance I am having NoSql background and in sql world I feel like I need achieve:

  1. Single responsibility in tables
  2. Get rid of a lot of redundant null’s
  3. Feels like self referencing column is an anti-pattern, which is public field is referencing to other rows id.

All suggestions are welcomed.

Desktop application does not run my program, while running it on the command line works

I usually run my game using the following command:

/path/to/proton /path/to/game.exe

I created the following desktop app:

[Desktop Entry]
Exec=/path/to/proton /path/to/game.exe

But nothing happens when I launch this app. How is it possible?

web application – watch out for directory traversal/path traversal security problem

After some research on the internet and read some articles/posts about directory traversal/path traversal security problem, I still don’t quite get when I need to watch out for this kind of security problem, should I always need to watch out for this kind of security problem when I am developing a back-end or only when I am doing/implementing certain things/features?

Designing Community Page UX for an Immigration Application

One of the ways I improve my website design and usability skills is by looking at other people’s critiques on websites. I used to like Concept Feedback but it has closed down.

How do I find similar sites?

(Please don’t tell me to Google it. I did. I am trying to post this question in an acceptable SE Q&A format)

web application – Securing session storage and whether appropriate for Open Banking

I’m currently building a web application that utilises Open Banking through Plaid. This means that it pulls a users banking details through a generated ‘access token’.

I’ve been toying with the concept of how to persist this user data. My reasoning for this is that the Plaid API gets pulled on every web page that requires it, and so it causes a several second ‘loading’ to process – which if you’re navigating round my app is frustrating.

This is a poor user experience in my opinion, and so I’d prefer to somehow persist this data without having to make a server call.

To do this, I’ve initially gone for session storage. I know many people say this is vulnerable to things such as XSS etc, but it’s convenient and works well.

I’m a little uneasy with storing the results of a server call locally though, for obvious reasons.

Currently, the data which is pulled and therefore stored locally is:

  • Firebase user ID
  • Account id
  • Balance
  • Type of account
  • Last four digits of account number
  • Account provider
  • Consent expiration time
  • Transactions
  • Database ID

And a bunch of other status codes.

The actual data itself isn’t personally identifiable, or usable for anything malicious to my knowledge. No passwords are stored locally, the access token is only ever exchanged via my server, and it is encrypted so not publicly visible as plain text should my database ever get hacked.

So I guess my question is, how secure is this? Is it actually a security problem considering the data can’t be explicitly used for malicious purposes? The only time it would be a problem (in my opinion) would be if my server / database was accessed with the encryption key.

Other alternatives are..

  • Encrypt the data that is stored in session storage, but is this pointless?
  • Not use session storage at all

Or can anybody suggest any other alternatives?

I know people on here will be much more experienced than me with this – so open to any suggestions. Please let me know, it’d be appreciated.

What is a responsible design/web application? It is just being responsive and accessible?

I came across the interesting term “responsible applications” used in an article, which proposes that an application that is responsible to the users is one that both responsive and accessible.

It could be argued that a responsive website caters for a range of devices and interactions, while an accessible website caters for users of different abilities and therefore both aspects encourage diversity and inclusion.

However, for a design to be truly ethical, and for the resulting application to not be harmful to the user, is that enough to cover all the bases? Do we need anything else?