A method in a mobile communications environment, the method comprising: when a first and a second mobile computing device with a relationship which is defined in advance are not yet connected, because they are not in close proximity, one or more applications each identifying a content file, the content file being added to a content list for later transfer; waiting for the related mobile computing device or a server to which the related mobile computing device will couple to be detected via a monitor as being in proximity; the method further comprising an override option, in which a user can specify that the content file is to be sent to a particular mobile computing device regardless of any proximity-based non-cellular connection status; in the first mobile computing device, detecting (404, 506) proximity to the second mobile computing device with which the first mobile computing device has a defined relationship; the method comprising the monitor recognizing the related telephone as being in its related telephone list, telling a process manager that the other mobile computing device is nearby, and telling the process manager the name or identity of the other computing device; and changing (414, 510) at least one operation in the first mobile computing device based on detecting the proximity, wherein changing the at least one operation comprises transferring content from the first mobile computing device to the second mobile computing device via a non-cellular communications coupling, comprising evaluating whether there are any content files pending for transfer to the related mobile computing device, making a short range non-cellular communications coupling, if there is at least one content file to be sent, the process manager sending the content file or an identifier thereof by which the file may be accessed to a transmission module, and telling the transmission module the identity of the recipient mobile computing device or server; the transmission module transferring the data, and if the data was sent successfully, the transmission module notifying the process manager that the data was sent out and the process manager removing the data file from the content list, wherein an unsuccessful transmission results in the entire data file being re-sent, or some part thereof being resent, provided that a transmission file is capable of informing the process manager as to what part or parts was successfully sent, and the recipient can accept partial data and build up the content file. when a first and a second mobile computing device with a relationship which is defined in advance are not yet connected, because they are not in close proximity, one or more applications each identifying a content file, the content file being added to a content list for later transfer; waiting for the related mobile computing device or a server to which the related mobile computing device will couple to be detected via a monitor as being in proximity; the method further comprising an override option, in which a user can specify that the content file is to be sent to a particular mobile computing device regardless of any proximity-based non-cellular connection status; in the first mobile computing device, detecting (404, 506) proximity to the second mobile computing device with which the first mobile computing device has a defined relationship; the method comprising the monitor recognizing the related telephone as being in its related telephone list, telling a process manager that the other mobile computing device is nearby, and telling the process manager the name or identity of the other computing device; and changing (414, 510) at least one operation in the first mobile computing device based on detecting the proximity, wherein changing the at least one operation comprises transferring content from the first mobile computing device to the second mobile computing device via a non-cellular communications coupling, comprising evaluating whether there are any content files pending for transfer to the related mobile computing device, making a short range non-cellular communications coupling, if there is at least one content file to be sent, the process manager sending the content file or an identifier thereof by which the file may be accessed to a transmission module, and telling the transmission module the identity of the recipient mobile computing device or server; the transmission module transferring the data, and if the data was sent successfully, the transmission module notifying the process manager that the data was sent out and the process manager removing the data file from the content list, wherein an unsuccessful transmission results in the entire data file being re-sent, or some part thereof being resent, provided that a transmission file is capable of informing the process manager as to what part or parts was successfully sent, and the recipient can accept partial data and build up the content file.