...
James isn't in a great hurry, but their current house is getting too small. They are both busy working their daily jobs and at the same time, want to keep up to date on the current housing situation in the area they would like to move into. They check these apartments form oikotie multiple times a day, alone from work, and review the options together in the evening. If they find anything interesting, they will ask advice from relatives and friends who know more about these issues.
feature importance
Generally, developers might assume the most important features for the application are the accuracy, proficiency and reliability since they can have an effect on the user's financial situation. The ease of learning and convenience are not necessarily that important, since buying an apartment is a serious issue, with what a user is able and usually willing to invest more effort to get things right.
On the other hand, the user convenience and and satisfaction cannot be overlooked, because the user might just give up if the software is too complex, incoherent or inconsistent. In this kind of situation, the user probably learns the system, no matter how long it takes, and then uses it until the apartment is found, and then forgets it completely. In this case, the site has received it's slice of the money, and the user might not be returning to the site anytime soon. If the user needs another apartment in the future, he probably thinks about the whole experience and the overall price, and the retention of learning doesn't matter much
For James over there, the valuable features might be convenience, efficieny, reliability and accuracy. Convenience and efficieny is needed if James wants to continuously check the apartments. Reliability and accuracy are needed when making the financially big decisions.