> For the complete documentation index, see [llms.txt](https://docs.tactyc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tactyc.io/technical/recommendations.md). # Recommendations ## Recommended Technical Specifications All of Tactyc computations are done in software code (i.e. JavaScript/TypeScript) and on your browser. The speed and performance of your user experience depends heavily on your browser version. We recommend using the following browsers for Tactyc: * Google Chrome: 55 and higher * Safari: 49 and higher * Firefox: 10 and higher Given Tactyc's quantitative heavy dashboards, mobile devices are not fully supported currently. Please use Tactyc in a desktop environment. ## **Concurrent Users Warning** If multiple users are concurrently are simultaneously changing data for a fund, Tactyc will honor the **last saved** changed for an investment or a fund. This might result in not all the changes being captured if one of the users does not have the latest session data. **Recommendation:** Please avoid having multiple users change data at the same time. The best practice is to have one single user editing at a time, while other users are viewing in read-only mode. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tactyc.io/technical/recommendations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.