Web applications
React and Angular can support browser-based application interfaces connected to the wider application environment.
Technology Solutions
Application Development
RothurTech supports custom application development, web and mobile experiences, APIs, microservices, defined changes to existing applications, QA automation, and application support across approved technology stacks.
Custom application development
Support application work from new development through ongoing use.
Application needs can involve a new system, an existing application, connected services, automated quality checks, or continuing support.
RothurTech supports Java and Spring Boot, .NET, Python, Node.js, React, Angular, mobile development, REST APIs, GraphQL, microservices, database development, QA automation, and application support.
These capabilities can support technology professionals joining client delivery teams or independently scoped, statement-of-work-based project delivery. The appropriate model and engagement terms are determined for the specific need.
Web and mobile applications
Build application experiences for the intended users and context.
Application discussions can connect the user experience, supporting services, and data needs without treating every application as the same kind of build.
Mobile development
Mobile development can support application experiences designed for mobile use and their required service connections.
Application services
Java and Spring Boot, .NET, Python, and Node.js can support server-side application responsibilities.
Database development
Database development can support the data structures and access needs connected to an application.
API and microservice development
Connect application responsibilities through defined interfaces.
APIs and microservices can be considered where systems or application components need clearly defined connections.
REST APIs
REST APIs can provide defined service interfaces for application and integration needs.
GraphQL
GraphQL can support application data interactions where it fits the agreed technical context.
Microservices
Microservices can separate application responsibilities when that architecture fits the system and delivery context.
Service and data coordination
API, microservice, and database work can be discussed together where the application depends on coordinated service and data behavior.
Existing applications
Plan application change around the existing environment.
Work on an existing application begins with its current responsibilities, dependencies, technology stack, and support context.
Current-state context
Identify the application responsibilities, technologies, data connections, and dependencies relevant to the proposed change.
Application components
Discuss where approved frameworks, APIs, microservices, or database development may fit the defined application change.
Quality considerations
Include QA automation and application-support needs in the application-change conversation.
Quality engineering
Connect QA automation to the application context.
QA automation can support repeatable checks for application work when the test scope, environments, responsibilities, and acceptance context are defined for the engagement.
Test scope
Identify the application behaviors, interfaces, and data interactions included in the agreed quality-engineering work.
QA automation
Apply QA automation to the checks and environments established for the specific application context.
Delivery coordination
Coordinate quality-engineering activity with the responsibilities established for the delivery team.
Application support
Keep support connected to the application’s operating context.
Application support can be discussed for existing systems, newly developed work, or defined application changes.
Support context
Clarify the application components, environments, dependencies, and team responsibilities within the support need.
Issue coordination
Organize application questions and issues according to the responsibilities agreed for the engagement.
Application change
Connect approved application-development capabilities to support-related changes when they are included in scope.
Delivery models
Choose how Application Development support fits the team.
The same capability area can be supported through two different models. The selected model establishes how responsibilities are organized for the specific engagement.
Professionals joining client delivery teams
Application professionals can join a client delivery team and work within the client’s delivery structure, responsibilities, and technology environment.
Independently scoped project delivery
Application work can also be organized under an independently agreed statement of work (SOW). Scope, responsibilities, deliverables, timing, and commercial terms are established for that engagement.
FAQ
Application Development questions.
These answers clarify the supported capabilities and delivery models.
Which application technologies does RothurTech support?
Approved capabilities include Java and Spring Boot, .NET, Python, Node.js, React, Angular, mobile development, REST APIs, GraphQL, microservices, database development, QA automation, and application support.
Can support include both web and mobile applications?
Yes. React and Angular are approved web-application capabilities, and mobile development is also included in RothurTech’s approved scope.
Can API and microservice work be included?
Yes. REST APIs, GraphQL, and microservices are approved capabilities. Their use depends on the application context and agreed engagement scope.
Can RothurTech support changes to an existing application?
Yes. An agreed engagement can address an existing application’s approved technology, API, microservice, database, QA automation, and application-support needs.
Does Application Development require a full project engagement?
No. Technology professionals can join client delivery teams, or application work can use independently scoped, statement-of-work-based project delivery.
What should an initial Application Development discussion cover?
Useful context includes the application need, current technology environment, users, systems and data connections, delivery-team context, and the capabilities being considered.
Application Development conversation
Discuss the application and delivery context.
Share the application need, current environment, approved technology capabilities involved, and which delivery model you want to discuss.