Customizing user interface experiences for requesters of transportation services

1. A method comprising:

detecting, by a transportation matching system comprising one or more servers, a mobile application session on a requester device;

detecting, by the transportation matching system, a location of the requester device;

determining, based on information associated with the location of the requester device, a demand severity metric for the mobile application session on the requester device;

identifying, based on the demand severity metric, one or more modifications to a user interface experience for the mobile application session on the requester device; and

modifying, in accordance with at least one of the one or more modifications, the user interface experience for the mobile application session on the requester device.

2. The method of claim 1 , wherein identifying the one or more modifications is further based on user profile information associated with a user of the requester device.

3. The method of claim 1 , further comprising:

predicting a time interval after which the demand severity metric will decrease; and

modifying the user interface experience for the mobile application session by presenting one or more incentives to delay a transportation request until after the time interval.

4. The method of claim 1 , wherein modifying the user interface experience for the mobile application session comprises adding one or more additional actions required by a user of the requester device prior to submitting a transportation request.

5. The method of claim 1 , wherein modifying the user interface experience for the mobile application session comprises presenting an offer to utilize an alternate transportation method to an alternate location having a lower demand severity metric.

6. The method of claim 1 , further comprising:

detecting, by the transportation matching system and within a common location with the requester device, a second mobile application session on a second requester device associated with a second user; and

determining, based on user profile information associated with the second user, not to modify the user interface experience for the second user.

7. The method of claim 1 , further comprising:

identifying location information for a transportation request associated with the requester device; and

determining whether to target the requester device based on the location information for the transportation request associated with the requester device.

8. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause a computer system to:

detect a mobile application session on a requester device;

detect a location of the requester device;

determine, based on information associated with the location of the requester device, a demand severity metric for the mobile application session on the requester device;

identify, based on the demand severity metric, one or more modifications to a user interface experience for the mobile application session on the requester device; and

modify, in accordance with at least one of the one or more modifications, the user interface experience for the mobile application session on the requester device.

9. The non-transitory computer-readable medium of claim 8 , wherein identifying the one or more modifications is further based on user profile information associated with a user of the requester device.

10. The non-transitory computer-readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computer system to:

predict a time interval after which the demand severity metric will decrease; and

modify the user interface experience for the mobile application session by presenting one or more incentives to delay a transportation request until after the time interval.

11. The non-transitory computer-readable medium of claim 8 , wherein modifying the user interface experience for the mobile application session comprises adding one or more additional actions required by a user of the requester device prior to submitting a transportation request.

12. The non-transitory computer-readable medium of claim 8 , wherein modifying the user interface experience for the mobile application session comprises presenting an offer to utilize an alternate transportation method to an alternate location having a lower demand severity metric.

13. The non-transitory computer-readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computer system to:

detect, within a common location with the requester device, a second mobile application session on a second requester device associated with a second user; and

determine, based on user profile information associated with the second user, not to modify the user interface experience for the second user.

14. The non-transitory computer-readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computer system to:

identify location information for a transportation request associated with the requester device; and

determine whether to target the requester device based on the location information for the transportation request associated with the requester device.

15. A system comprising:

at least one processor; and

at least one non-transitory computer-readable storage medium storing instructions that, when executed by the at least one processor, cause the system to:

detect a mobile application session on a requester device;

detect a location of the requester device;

determine, based on information associated with the location of the requester device, a demand severity metric for the mobile application session on the requester device;

identify, based on the demand severity metric, one or morel modifications to a user interface experience for the mobile application session on the requester device; and

modify, in accordance with at least one of the one or more modifications, the user interface experience for the mobile application session on the requester device.

16. The system of claim 15 , wherein identifying the one or more modifications is further based on user profile information associated with a user of the requester device.

17. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to:

predict a time interval after which the demand severity metric will decrease; and

modify the user interface experience for the mobile application session by presenting one or more incentives to delay a transportation request until after the time interval.

18. The system of claim 15 , wherein modifying the user interface experience for the mobile application session comprises adding one or more additional actions required by a user of the requester device prior to submitting a transportation request.

19. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to:

detect, within a common location with the requester device, a second mobile application session on a second requester device associated with a second user; and

determine, based on user profile information associated with the second user, not to modify the user interface experience for the second user.

20. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to:

identify location information for a transportation request associated with the requester device; and

determine whether to target the requester device based on the location information for the transportation request associated with the requester device.