7 replaced http://ux.stackexchange.com/ with https://ux.stackexchange.com/
source | link

So are the suggestions good ones, or are they going to hinder the use of the application?

  • Drag to share: worth a try.
  • Bouncing buttons: imho god no. Reminds me of these two:

    enter image description here enter image description hereenter image description here

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

Keep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

So are the suggestions good ones, or are they going to hinder the use of the application?

  • Drag to share: worth a try.
  • Bouncing buttons: imho god no. Reminds me of these two:

    enter image description here enter image description here

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

Keep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

So are the suggestions good ones, or are they going to hinder the use of the application?

  • Drag to share: worth a try.
  • Bouncing buttons: imho god no. Reminds me of these two:

    enter image description here enter image description here

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

Keep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

6 tried to make first look at post more interesting
source | link

So are the suggestions good ones, or are they going to hinder the use of the application?

  • Bouncing buttons: imho god no. Sounds like trying to click this bouncing ball, and reminds me of this troll post. :)
  • Drag to share: worth a try.
  • Bouncing buttons: imho god no. Reminds me of these two:

    enter image description here enter image description here

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

Keep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

So are the suggestions good ones, or are they going to hinder the use of the application?

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

Keep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

So are the suggestions good ones, or are they going to hinder the use of the application?

  • Drag to share: worth a try.
  • Bouncing buttons: imho god no. Reminds me of these two:

    enter image description here enter image description here

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

Keep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

5 tried to make first look at post more interesting
source | link

So are the suggestions good ones, or are they going to hinder the use of the application?

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if, but only if you believe in them in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

BalanceKeep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Balance

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

So are the suggestions good ones, or are they going to hinder the use of the application?

Is the key to creating standout applications implementing crazy ideas?

Yes, but only if you believe in them, and are ready to remove them if they happen to not work out. Innovation includes trial and error.

Now for the ranting:

Keep the balance between standards and experiments

They say standard stuff is boring. I say standard stuff is great stuff. Buttons should not bounce. Common controls like navigation elements and buttons has kind of a behavioural contract. The basic expectations on common controls should be met. Buttons are expected to stand still.

The more standards you use, the easier it will be to add on new ideas. In an environment that feels solid and where users can rely on controls doing what they are expected to do, there is more room for experimental ideas, than if all standards would been thrown out the window.

Choose your experiment

You write that it is a university assignment. I guess that there will not be many users suffering from potential bad design choices. This might actually be one of your best opportunities in life to spin crazy ideas without insulting neither users or designers, and this way practising just how crazy you can make an app.

Maybe bouncing buttons is not the idea you want to spend time on, but it can be made more interesting, for example "How can we get the bouncy effect without pulling Charlie's football?" or "How can we [insert crazy idea here] without hindering the use of the application?", and so on.

Good luck and have fun! :)

4 added 57 characters in body
source | link
3 added 57 characters in body
source | link
2 added 408 characters in body
source | link
1
source | link