Tag Info

New answers tagged

0

You may also try to: Group your data by location for different zoom levels, i.e. show a single icon for several items at abstract zoom level 0 and draw items separately on a zoom level 1. Caching data for lower zoom levels will give you a nice boost. Fetch data from the server by small chunks and render this chunks data to the user: it will let user to see ...


1

Firstly - optimise the size of your data and your indexes. 29000 rows is a small dataset for a well indexed database to handle - suggest you read up on covering indexes: http://en.m.wikipedia.org/wiki/Database_index#Covering_index The next stage is to consider that it makes zero sense to present 29000 icons to a user. Take a leaf out of Google's book and ...


0

How fast something feels depends on the absolute objective time the operation takes and a perception component, which is more subjective and can be slightly manipulated. Some methods to consider: Can your data be displayed in layers (e.g. showing only hotels on the map, only restaurants, etc.)? If so, load one layer at a time and load the rest on demand ...


0

The above is a really elaborate and impressive answer. I would add that you need to ask 'what is important to know'. for instance: let's say that there is an increase of 2.003 in the number of blooming flowers. Now, you can show the number, you can show an arrow or you can show both. showing only an arrow will make the growth of 2.003 and 187.3 look the same ...


1

First of all, they could be perceived as subsets or specific cases of a continuum, common enough to get special treatment. But there are also differences. Alphabetical order is "arbitrary" to some extent, it doesn't tell you anything about the actual properties of an item. If you deal in clothing and your continuum is Size, you could say "I want to see the ...


0

You may want to start with getting some qualitative market research which will drive the high level spec of a product if you have a budget (this is what market research firms do), or doing some DIY 'talking to users' if you don't.


1

OAUTH has become an industry standard for federated signon systems. Google and Facebook both implement the protocol. When you signon to stackexchange with Google, that is OAUTH under the covers. As a web developer, you can either implement an OAUTH server yourself, which federates to each of your other sites, or another option is implementing Google, ...


0

The option with the least amount of work is using a third party. Google, Facebook etc. There are pros and cons to this, but from a UX perspective, this is probably the easiest and most trustworthy. Stack Exchange does this well. You can simply create a new account on any SE site and it links your accounts. They target an identifier, in their case, it's an ...


2

Your case is all about a third party identity provider. It does all the things above and more. You don't have to worry, at all. My banks (I have more than one) provide a Bank-ID valid for my both banks and a number of official state controlled sites. I can use my Bank-ID to sign in almost anywhere without creating an account, with the boring sign-up ...



Top 50 recent answers are included