Quora: the knowledge platform

Opening the app and the onboarding reality

Installing the Quora APK is a straightforward process. The app is available on the Google Play Store, but direct APK downloads are also possible through third-party sites. Once installed, opening the app presents a login screen. You can log in with an existing account or create a new one. The registration process is simple, requiring an email address and a password. The app does not offer a guest mode. You must have an account to proceed. After logging in, the app asks you to select topics of interest. This is a crucial step. The topics you choose will shape your feed. The app then shows a personalized feed with questions and answers from those topics. The feed is the core of the experience. It is a continuous stream of content. The app does not have a tutorial or onboarding guide. You are left to explore on your own. The interface is clean and functional. The bottom navigation bar has tabs for Home, Spaces, Notifications, and Profile. The Home tab shows the feed. The Spaces tab allows you to join and create spaces. The Notifications tab shows activity related to your account. The Profile tab shows your activity and settings. The app loads quickly on a decent connection. The initial load time is acceptable. However, the app can be slow to load content at times, especially with a poor connection. The app does not have an offline mode. All operations require an internet connection. This is a limitation for users in areas with poor connectivity. The overall first impression is that of a functional but content-heavy app. It is easy to use, but it can be overwhelming due to the sheer volume of content.

How the follow topics and ask a question features work together

The app includes a feature to follow topics and a feature to ask questions. These two features interact in a practical way that is not described on the Play Store page. A user can follow a topic, such as "Artificial Intelligence." The app then shows content related to that topic in the feed. The user can then ask a question within that topic. The app allows you to add topics to your question. When you ask a question, you can select relevant topics. The app then shows the question to users who follow those topics. This creates a workflow where following topics leads to more relevant content and questions. The app does not, however, automatically suggest topics based on your questions. You must manually select topics. The app also does not show you the topics that are most popular or trending. This is a missed opportunity for discovery. The current design requires the user to actively manage their interests. This can be time-consuming. The app's design philosophy seems to be to provide a collection of features. It does not aim to create an integrated user journey. The follow feature is useful for personalization. The ask feature is useful for getting answers. But the user is left to connect the dots. This is a common issue with many apps. They often focus on providing individual features rather than a unified experience. The app's potential is limited by this siloed approach. A more integrated design would make the app more valuable. It would allow users to easily transition from reading content to asking questions. The current design is a reflection of the broader challenges of content platforms. It is a step in the right direction, but there is room for improvement.

Real-world performance, bugs, and crashes

The app's performance is a mixed bag. During normal usage, the app is responsive. Scrolling through the feed is smooth. The search function works quickly. However, the app is prone to crashes and errors during peak usage. The most significant issue is server overload. The app relies on a central server to handle all requests. When many users access the app simultaneously, the server struggles. This was evident during the new student registration period in June 2026. The app was used for the PPDB process. Parents reported that the app was slow or unresponsive. Some could not even log in. Others could not upload documents. The server errors were widespread. The local news covered the issue extensively. The government acknowledged the problem. They cited technical constraints and server disruptions. The app's changelog mentions "Fix grid loker" and "Perbaikan stabilitas & bug kecil" (stability improvements & small bug fixes). This suggests that the developer is aware of the issues. However, the fixes seem to be incremental. The app still suffers from performance problems during high load. The app does not have a built-in mechanism to handle server errors gracefully. It simply shows a generic error message. This is frustrating for users. The app also lacks an offline mode. All operations require an internet connection. This is a limitation in areas with poor connectivity. The app's stability has improved over time. The version history shows several updates. The updates include bug fixes and performance improvements. The developer is actively maintaining the app. This is a positive sign. However, the app's architecture may need a fundamental redesign to handle peak loads. The current issues are a barrier to adoption. Users expect a reliable service. The app's performance during critical periods is a major concern. The app's real-world performance is acceptable for light usage. But it fails under pressure. This is a significant drawback for a government service app.

Permissions and data safety

The app's data safety section on the Play Store states that it does not share data with third parties. It also states that data is encrypted in transit. However, it also states that data cannot be deleted. This is a significant privacy concern. The app may collect personal information, device IDs, and other identifiers. The exact permissions are not listed on the Play Store page. This is a red flag. The app may request access to storage, camera, or location. These permissions are typical for apps that handle document uploads or media sharing. The app's privacy policy is not directly linked from the Play Store page. The developer's email is provided for support. The app is developed by Quora, Inc. This provides some level of trust. However, the lack of transparency on permissions is a concern. Users should be aware of what data the app accesses. The app's design emphasizes security. It uses registered accounts for access. This is a standard practice for corporate apps. The app does not appear to have any major security vulnerabilities. However, the server-side security is not documented. The app's data safety claims are positive. But users should still exercise caution. The app's permissions and data handling are not fully transparent. This is a common issue with many apps. The technical detail that stands out is the lack of permission listing on the Play Store. This is unusual for a modern app. It may indicate that the app does not request many permissions. Or it may indicate a lack of attention to detail by the developer. The app's data safety practices are a key selling point. But the lack of transparency undermines this. Users who value privacy may be hesitant to use the app. The app's permissions and data handling are a critical aspect of its technical profile. More transparency would build trust.