Why Radical Efficiency
Software development is expensive. We want to eliminate the stress of investments in software development efforts by providing radically efficient development services.
Here at Radency, we provide businesses with resourceful engineers who always strive to understand the business value of the product features they develop.
We believe this to be the key to radically efficient software development. Involved engineers who understand business goals always figure out when to optimize for rapid delivery and when to build solid foundations, when to integrate a third-party service and when to create a custom solution.
With the help of data-driven product managers, such an engineering team efficiently delivers just what the product needs at this stage - be it an MVP, a future-proof solution, a complex integration or a proof of concept for a product hypothesis.
We start every project with a careful prior analysis of the situation performed by our engineers and technical product managers:
Context
Product Vision
Budget
Timeline
Overall Priorities
Initial Priorities
Analysis
User Analysis
Market Analysis
Tech Analysis
Solution
Roadmap
MVP
Tech choices
Performance, Security, Availability Requirements
Product Hypotheses
What we mean by efficiency
Check out examples of decisions we implemented on our projects which proved to be efficient
Mobile app for E-learning platform
Choosing React Native as a cross platform technology for this platform yielded several benefits - it meant having a shared team for web and mobile, and shared a codebase for iOS and Android. This allowed us to be very flexible in balancing the workload among the existing team members. Furthermore, we relied on React Native’s rich ecosystem and used open-source cross-platform libraries for many crucial functions, such as the video player.
Serverless backend for Fantasy football
Choosing serverless architecture allowed us to focus on writing data processing logic without the need to set up extensive application infrastructure. Such architecture fits the job as there is not much foreseen extension or modification of the app logic. At the same time, it gives the benefit of scalability without the need to design for it - the platform will support as many users as needed.
Task API for Collaboration Software
We’ve lobbied the usage of GraphQL for querying tasks. As various task views required different data, this would require meticulous work on the backend implementing data presentations with filters, sorts and paginations. Using GraphQL eased the task significantly as we could implement the schema once and query all the permutations from the frontend without changing backend code. This was also useful for implementing a public API for tasks.