As discussed in #25, it would be helpful to provide a deployAndExecute function that would deploy the proxy and immediately call a target contract in the same transaction.

To quote @SolcAndMe:

The main drawback for a protocol / app to use proxy accounts for their users is user onboarding - in particular the very first interaction between the user and the app. Sequential transactions still lead to pretty janky UX - primarily in conveying to the user for why two transactions are being sent instead of just one and secondly it also is more expensive for the user because the base tx cost has to be paid twice. Adding that method to the factory leads to very minimal gas overhead.