I played with Anvil for the first time at PyConUK last weekend, and I was really impressed.
Specifically on the point of accessing your code:
- if you Architect your code well enough you can keep reasonable separation between generic Python code and code that is tightly-coupled to Anvil (I.e. keep it modular)
- and Anvil does actually provide a means for you to directly clone your Anvil app code locally from their servers using Git. This would give you a copy of all your code including front end templates etc.
I think tie-in is always a consideration but we are increasingly getting into that situation with things like AWS, and so we really must balance the pros and cons. I’d rather by tied in and profitable if I’m trying to get something off the ground...
Specifically on the point of accessing your code:
- if you Architect your code well enough you can keep reasonable separation between generic Python code and code that is tightly-coupled to Anvil (I.e. keep it modular)
- and Anvil does actually provide a means for you to directly clone your Anvil app code locally from their servers using Git. This would give you a copy of all your code including front end templates etc.
I think tie-in is always a consideration but we are increasingly getting into that situation with things like AWS, and so we really must balance the pros and cons. I’d rather by tied in and profitable if I’m trying to get something off the ground...