Recoverable/Unrecoverable Error with a Toast Notification

I’m working on a mobile app, and am trying to figure out how to display recoverable and unrecoverable errors in context with a list. If a list of items are fetched in the initial request, and a subsequent page fails to load, what should show to the user to inform about the error? Toast Notification?

In the current implementation, the toast notification shows at the top of the screen, pushing the content down. Not sure if this is the best approach and I wonder if I should have the toast floating at the top instead. Thoughts?

enter image description here

When should a toast should a-raise in web app (need psychological suggestion) why favourite doesn’t has toast but archive or delete has?

When should a toast should a-raise in web app (need psychological suggestion) why favourite doesn’t has toast but archive or delete has?

When should a toast should a-raise in web app (need psychological suggestion) why favourite doesn’t has toast but archive or delete has?

When should a toast should a-raise in web app (need psychological suggestion) why favourite doesn’t has toast but archive or delete has?

Toast Notifications for Incoming calls between users of UWP desktop application

We have created a windows 10 UWP desktop application which works similar to skype. We have chats and video call feature in the app. We also need a notification feature to send a toast notification when a customer calls another customer using this app.

I was able to send blank toast notifications from MS partner center “notification” option to all users of the windows 10 desktop app.

How do i send toast notifications for incoming calls between 2 users of the UWP desktop app. The toast notification should have option to reject and accept calls, if user is logged in.

Thanks Rahul

How long should a temporary notification (toast) appear?

For our intranet application we have little notification messages (toasts) that indicate successful operations like “information saved,” “logged out” etc. Most of them are not important enough to require a modal operation (like Stack Exchange’s “click to close” windows) so they close automatically after 2500ms and I’m trying to make them disrupt the user as little as possible. They are however important to present as users need confirmation an action was successful as it may be part of a repetitive or complex workflow.

I want to make sure they’re readable and understandable within the time frame so I was wondering if there was any research on how long it takes people to read information especially in a “pop up” style context. It’s not actually a pop up window, more like SE’s notification bar but it automatically goes away. If I could ballpark how long to expect reading to take it would help tune the duration of the message and the length of messages.

Does Toast cause the application to crash at any time ? [on hold]

when i just press on the signup button without entering any data in the app all the toasts work , but once i enter data and press the signup button the app craches without printing any toast ?

protected void onCreate(Bundle savedInstanceState) {     super.onCreate(savedInstanceState);     setContentView(R.layout.activity_main2);     signupnow=(Button) findViewById(R.id.button3);      signupnow.setOnClickListener(new View.OnClickListener() {         @Override         public void onClick(View v) {              Toast.makeText(Main2Activity.this,"passed test1", Toast.LENGTH_LONG).show();             nametext = (EditText) findViewById(R.id.editText4);             emailtext = (EditText) findViewById(R.id.editText);             passtext = (EditText) findViewById(R.id.editText2);             // no we have the input check the Email if its cottect or not             Toast.makeText(Main2Activity.this,"passed test2  text getters", Toast.LENGTH_LONG).show();              db = new DatabaseHelper1(getApplicationContext());              sessiondb=new logindatabase(getApplicationContext());             Toast.makeText(Main2Activity.this,"passed test3   database connections ", Toast.LENGTH_LONG).show();               String Email = emailtext.getText().toString();             String name = nametext.getText().toString();             String pass = passtext.getText().toString();             Toast.makeText(Main2Activity.this,Email+"--"+pass+"---"+name,             Toast.LENGTH_LONG).show();            Boolean Emailstat=false;              if (Email != null && name != null && pass != null) {                  Toast.makeText(Main2Activity.this,"passed test4   checking emails ", Toast.LENGTH_LONG).show();                  if (Email.contains("@yahoo.com") || Email.contains("@gmail.com") || Email.contains("@hotmail.com")) {                     Emailstat=true;                 }                     if(Emailstat==true)                 {                    int emailsignupstat=db.CheckSiqnupEmail(Email);                   if(emailsignupstat==0)                   {                    db.addData(Email,pass,name);             //   login database to add user as loged in                  sessiondb.addData(Email,pass);                       Intent gotoprofile=new Intent(getApplicationContext(),Main3Activity.class);                       startActivity(gotoprofile);                     }                   else                   {                       Toast.makeText(Main2Activity.this, "Email is Used         Before  ", Toast.LENGTH_LONG).show();                 emailtext.setText("");                 passtext.setText("");                 nametext.setText("");                     }                      }                 else                 {                     Toast.makeText(Main2Activity.this, "Wrong Email ", Toast.LENGTH_LONG).show();                     emailtext.setText("");                     passtext.setText("");                     nametext.setText("");                  }               }         }      });  } 

}