|"Is an iPhone a thick client?" no only the user. (drum roll)|
couldn’t help myself.
To iterate depends on what the iphone is doing.
The thin verses fat is dependent on how dependant it is on the server.
I’ll use a Google docs, a file server and ms word as an example and this is a bit woolly so no using it as an answer for your homework. It’s not 100% true just an example to highlight a point
If using Google docs you are acting as a thin client. the word document you are using is on the server not your local machine and every time you make a change to the spelling or font, the server where the file resides has to calculate all the changes and information like possible words that you meant and so on. So in this example all the processing is server side. This means the device you have doesn’t need to be powerful or have lots of processing since all the processing and storage is server side. All that is important is the connection and its heavily reliant on the connection. Any break in communications and you can’t work
In comparison if you are using a ms word document. Then when you contact the server the document is sent to the pc. The document is stored on the pc and when you change font or spell check the processing is on the pc. Then at the end when you hit save the file goes back to the server and is stored. So the fat client needs more processing, storage and less reliant on the connection.
But they are just black and white examples in reality things are greyer. And you cannot look at the hardware and say either way. it’s how they interact with the server that is the key