This is a hard question to answer in the abstract. What are the top 2-3 questions you want to answer?
If it's about understanding the users of your app and what they look like, GA probably wouldn't be a good choice even if you didn't have a single page app because it's tailored for tracking activity across all users, not activity broken down by user. (For instance, it's good at answering the question, "Which feature gets the most usage?" not, "Which feature is used by the most people?" and that's an important difference.)
Many analytical tools claim they can answer the latter question, but look for example use cases to make sure they're answering the right question. A little research up front can save you the time of integrating a service only to find it doesn't answer the questions you want answered.
Comments
This is a hard question to answer in the abstract. What are the top 2-3 questions you want to answer?
If it's about understanding the users of your app and what they look like, GA probably wouldn't be a good choice even if you didn't have a single page app because it's tailored for tracking activity across all users, not activity broken down by user. (For instance, it's good at answering the question, "Which feature gets the most usage?" not, "Which feature is used by the most people?" and that's an important difference.)
Many analytical tools claim they can answer the latter question, but look for example use cases to make sure they're answering the right question. A little research up front can save you the time of integrating a service only to find it doesn't answer the questions you want answered.