typescript – Are there technical issues/disavdantages on this BaseService that aims to simplify calling API endpoints

I have created an angular BaseService that aims to simplify calling API endpoints

I would like to know if you see any code smells, bad patterns or architecture issues.
What disadvantages could this have.

The idea is to decouple the api configuration from the implementation

The configuration is made in the api-config.ts

export enum ENDPOINT {

export enum VERB {

export class ApiConfig {
    endpoint: ENDPOINT;
    url: string;
    verb: VERB;

const API_CONFIG: ApiConfig() = (
        url: '/cfg/getMenu',
        verb: VERB.GET
        url: '/cfg/getCSMO',
        verb: VERB.GET_BY_PARAMS
        url: '/aat/post',
        verb: VERB.POST_BODY
        url: '/aat/delete',
        verb: VERB.PATCH
        url: '/dsh/getCNSD',

export { API_CONFIG as API_CONFIG };

Then the baseService exposes a call method that determine what verb needs to be called and is the only place where httpClient is used

import { Injectable } from '@angular/core';
import { HttpClient, HttpParams } from '@angular/common/http';
import { ConfigService } from 'src/app/app-config.service';
import { Observable } from 'rxjs/internal/Observable';
import { ApiConfig, API_CONFIG, ENDPOINT, VERB } from './api-config';

class CallOptions {
    body?: any;
    params?: HttpParams;
    queryString?: string;

export class BaseService {

    constructor(protected httpClient: HttpClient, private configService: ConfigService) { }

    public call(apiEndpoint: ENDPOINT, opt: CallOptions): Observable<any> {

        const verb = this.getConfig(apiEndpoint).verb;

        switch (verb) {
            case VERB.GET:
                return this.get(apiEndpoint);
            case VERB.GET_BY_PARAMS:
                return this.getWithParams(apiEndpoint, opt.params);
            case VERB.PATCH:
                return this.patch(apiEndpoint, opt.queryString, opt.params);
            case VERB.POST_BODY:
                return this.post(apiEndpoint, opt.body);
            case VERB.POST_BODY_PARAMS:
                return this.postWithParams(apiEndpoint, opt.body, opt.params);
                const error = `BaseService: Verb ${verb} not supported yet`;
                throw new Error(error);
    //TODO if migration is finished convert this to private, it should not fail compiling
    protected getBaseUrl(): string {
        return this.configService.get('apiUrl');

    private getConfig(apiEndpoint: ENDPOINT): ApiConfig {
        const apiConfigEndpoint = API_CONFIG.find(e => e.endpoint === apiEndpoint);
        if (apiConfigEndpoint === undefined) {
            const error = `BaseService: Endpoint (${apiEndpoint}) not configured`;
            throw new Error(error);
        return apiConfigEndpoint;

    private buildURL(apiEndpoint: ENDPOINT) {
        return `${this.getBaseUrl()}${this.getConfig(apiEndpoint).url}`;

    private get(apiEndpoint: ENDPOINT): Observable<any> {
        return this.httpClient.get<any>(this.buildURL(apiEndpoint));

    private getWithParams(apiEndpoint: ENDPOINT, params: HttpParams): Observable<any> {
        return this.httpClient.get<any>(this.buildURL(apiEndpoint), { params });

    private post(apiEndpoint: ENDPOINT, body: any): Observable<any> {
        return this.httpClient.post<any>(this.buildURL(apiEndpoint), body);

    private postWithParams(apiEndpoint: ENDPOINT, body: any, params: HttpParams): Observable<any> {
        return this.httpClient.post<any>(this.buildURL(apiEndpoint), body, { params });

    private patch(apiEndpoint: ENDPOINT, queryParams: string, params: HttpParams): Observable<any> {
        return this.httpClient.patch<any>(`${this.buildURL(apiEndpoint)}?${queryParams}`, params);

Since the call method returns an Observable it can be used in the same places and in the same way as when calling httpClient get or post methods

loadMenu$ = createEffect(() => this.actions$.pipe(
        switchMap(() => this.baseService.call(ENDPOINT.CONFIGURATION_GET_MENU, {})
                map(response => actions.loadMenuComplete({ menu: response.result })),
                catchError(() => of(actions.loadMenuFailure({ error: 'fail' })))

if project treble aims to separate the platform and vendor partitions, why is the kernel source code needed when building system.img (platform)

if project treble aims to separate the platform and vendor partitions so they can be updated separately, why is the kernel source code needed when building system.img (platform) for AOSP, isn’t the kernel source code provided by the vendor side?

p.s is the kernel source code used to build the core system/framework files or is it only used in the boot.img/recovery.img?

Elements that you must define before creating an app

Mobile app has become an important element in any business. Although it is a fundamental element to accelerate growth, developing an app without targets does not produce favorable results.


Achievable goal and audience for which the app is intended. It is important that you determine if you want to increase the image of your brand or the sale of products, the sale of services, the facilitation of your employees' work, and so on. If the mobile application is directed to your employees, the professionals are from a particular business field, etc.

Intention to expand in the future

It's not the same thing to need a simple application that takes a concrete action that requires something more complex, with many options and content, to build an entire business model. Build the scope of your app and its requirements for the future.

user experience

There are certain business models that we are accustomed to gaining experience with using a web browser or browser experience app. To properly identify this point, you would need to do a small study to see how the user experience is evolving in every business. Now you want to publish the mobile application.

Level of user experience

At this point, you need to understand the complexity of the design and the importance you attach to the user experience. It may require a completely customized design with optimal response times that should stand out and be a reference on the market.


The mobile application can be compatible with all operating systems and mobile devices, or we are only interested in a specific operating system such as iOS or An.

Access and use of mobile resources

The mobile application may need to use the push notifications of the mobile phone, the camera (photos, scanning bar codes, scanning QR codes), the microphone (voice recognition), the calendar, the GPS to use the geographic location other to complete the offered functions. For example, Facebook's mobile application accesses mobile notifications to inform us about activities on our wall or profile.

Distribution channel of the application

We may be interested in the user who downloads the mobile application from the operating system market of his smartphone (Google Play for users of the operating system An ♪♪♪♪♪ and Apple App Store for iOS users) or, on the contrary, if you prefer that Users do not need to download anything and access it from the mobile browser.

Offline operation (offline mode)

We need to determine if it is necessary to use the mobile application at times when users may not have an Internet connection. For example, the mobile application of newspapers allows us to download messages when we have an Internet connection and access them when we do not have them, because we are on the go, or simply because we do not want to spend our data bonus and download when we connect us with a Wi-Fi network.

Economic budget

How much money do you want to spend? Because native apps are more expensive than web apps or HTML5 apps, creating a budget plan can select an app that takes into account not only your business goals but your financial plan as well.

If you keep these 9 elements in mind before creating an app, you can be successful in the marketplace. The mobile application is more of a strategy than a technical development. Therefore, components of corporate values ​​and vision must be considered.


Disregarded rules about WEBSITE DESIGN

Website templates allow you to create a website, whether you have no design options, time, or an enormous spend budget. Website creation templates can also save you time, effort, and money – just in case you choose the right one! The wealth of web design templates can be breathtaking, but with a few simple queries, you can come to an informed decision before creating a website.

If you are considering different website templates, you should be sure about the website goals. If you know what you need to specify and what guests have to do, you are ready to select a format and create a website! With regards to your goals, you can navigate with simple improvements in the field of web design templates. Mobile App Development Company follows the rules during website development.

What kind of website do you want to create?

Website templates define the structure and appearance of a website. Create a single page? Do you need 10 pages mostly text? Or do you need a directory with thousands of product images? You also need the web design template with the design when you develop a website.
Which layout suits your needs?

The layout determines how the information is structured when you create a website. The key to using web design templates is selecting the template, which works exactly how it is needed and without too many changes. Avoid website templates that look good but that want to adapt the excessive redesign to your practical needs. When creating a website, keep in mind the structure of the home page and inside pages. Do you mainly want text pages? Are you adding graphics, tables and links? Do you like the navigation bar at the top or to the side?

Do the web design templates require many customizations?

In most web design templates, you can make changes to reflect your existing brand. The customization ranges from color and font choices, to adding your company logo, to adding multimedia and Flash animations. Which adaptation do you need? Keep in mind that web design templates must meet the goals of fast download time, be search engine friendly, and make navigation easy for the user. Make sure that the template you choose to create a website supports the required level of customization.

Is customer service available for you?

No matter how "easy to use" or "easy to update" – website templates must be kept by an expert who can help you with problems. 24/7 Support Is Important When Creating a Website Make sure that you can reach someone by phone, email or online chat so that you can really get your website up "anytime" at any time of the day or night can upload.

Are the website templates professionally designed?

There are many web design templates at different costs. It is certainly important to choose the website template that reconciles professional design with ease of use. The goal of a web page is to guide the viewer to a selected action. It should look good, be legible, download quickly, be readily available to search engines, and work in all web browsers. Web design templates must be created by both web designers and programmers to ensure that design and usability are perfectly aligned.

Web design templates can save you time, money and effort in creating a website. The right template for your website will give you a great look and will have all the features you need to focus on what you add to your website instead of getting it up and running.


google – The process automation robotics project aims to analyze how AI elements can be inserted into an existing system to improve efficiency or performance?

I am 18 years old and am studying at an IT college. So, this college gives me an assignment with attribution title is efficiency and performance AI. So I decided to write an RPA Artificial Intelligence project. But please help me, I want to know the key objectives and goals for an RPA artificial intelligence project to improve performance and efficiency. Can you help me??

Need help for nearby keywords. Please help someone

Need help for nearby keywords. Please help someone

+ Answer to thread

  1. Need help for nearby keywords. Please help someone

    Hello everyone!
    I have an SEO project that targets some keywords that are close to me. My question to you is how to use SEO for these keywords. A detailed answer is appreciated.

booking permissions

  • you not allowed post new threads
  • you not allowed post reply
  • you not allowed Post attachments
  • you not allowed Edit your posts



5 Bugs in budgeting mobile apps

Mobile App Costing is a task for which many companies are not sufficiently prepared. Despite the importance of mobile and the number of organizations that understand its importance, it's amazing how little you know what it's about to build a fully functional, ready-to-use mobile app. The result of this knowledge gap is that many of the time, resources, and budgets required to build a useful product are often underestimated. In our experience, the biggest mistakes in budgeting mobile apps are:

1. Ignore the backend development / infrastructure requirements
2. Misunderstanding of the great differences between apps and websites
3. Do not consider the cross-departmental connection required for delivery and ongoing success
4. Insufficient marketing budget to promote and educate customers on the mobile app
5. No update schedule to meet customer requirements after the early start

The speed of mobile app development varies from case to case, and factors such as scope, complexity, functional requirements, and the company you choose to partner ultimately determine the cost of your project. We'll discuss each of the errors listed above and why these areas are essential when you're creating a budgeting plan for mobile apps. At the end of this article, you will have a broader understanding of the time, effort and expense associated with creating a popular mobile app.

Ignore backend development and service integration

The biggest flaw in budgeting mobile apps is the assumption that it's a stand-alone product consisting only of the screens that users interact with on their devices. The reality is that the app's interface is a very small part of a larger machine that makes the app work.

There are a number of moving parts: the Content Management System (CMS); the backend infrastructure APIs that process business logic (cloud-based); and third-party integrations. We look at this:

CMS (Content Management System): The CMS for mobile offers configuration and content services. Do not think about WordPress. Think mobile to get the best mobile experience. You do not want to republish an app if an API endpoint has changed or a backend maintenance window. The mobile CMS should be seen as part of the mobile app, offering everything from settings, menu details, images and text content to application.

Backend infrastructure culture: Your app expects you to need to communicate with a server to perform actions that can not be performed on the device. These include authentication, business integrations such as scheduling appointments, requesting status updates, business processes, notifications and messages, etc. I have considered these services to be core services that you should actually consider from a mobile context. Your customers do not want to wait for answers. Mobile specific services that are extremely responsive are the only true solution in the world today.

Echo Innovate IT describes the backend infrastructure as "a critical part of developing mobile apps because that's where the value lies. An app by itself is nothing if it does not process the right data on time. "

Third-party integrations: You do not want to do everything from scratch. Therefore, look for third-party vendors that offer optimal solutions to dot problems. Push notifications, analytics, authorization, and authentication are just some of the things that need to be considered.

Some make the mistake of only considering the frontend when setting a mobile app budget. In this way, they ignore the biggest cost drivers that are typically in the backend infrastructure and integrations that are not immediately visible.

We can tell from the favorite example of all: Uber. First, Uber has two different apps. The first is what the users see, which allows them to order the service, manage their accounts, etc. Another is the app that the drivers use. Even if it's just a single app, the amount of backend infrastructure and integration the app needs to work would surprise many. You have the location and map components. a payment / transaction system; dynamic pricing model that is created when needed; and much more.

Take a look at Uber's failure of her tech stack. Applications that require this kind of infrastructure are expensive to build and scale. Uber's initial funding was $ 1.5 million, with much more capital acquired in subsequent phases.

While Uber is a complex example, it identifies the many facets needed to make an app work, and many ignore it when designing a mobile app budgeting plan.

The thinking of mobile apps and websites does not differ significantly

Apps do not just need the back-end infrastructure. All of these different components need to be integrated for the application to work. Ensuring that all moving parts – front-end, CMS, third-party services, back-end – work together effortlessly takes a lot of time and effort. much more than a website. The more complex the project, the more time and effort are involved. the more it costs.

In almost all cases, the infrastructure must be built absolutely. Existing services that were not originally designed for mobile devices are not enough. Internal and legacy systems are expected to be rebuilt to support mobile devices.

The trap that many organizations come up with is that their current services are good enough.

Disregard for cross-departmental engagement

The well-known saying "It takes a city" may not be suitable for versatile application improvements. As there are a variety of variants in the specialized segments required for an application, it is necessary that attachment be made across internal groups for the application to be fruitful. Progress is only part of the picture.

For an average application facing competitors, you should specify a number of business capabilities: IT, design, presentation, offerings, and key partners. Effective items will have an inner hero, however, the individual should not be the main colleague.

It is also expected that promotions and offers drive customer safety and development, and for different companies that rely on your application's idea. For example, if your customization plan depends on publishing, you must bid to make room. If you intend to make in-application presentations or enhancements, your promotion group should be included.

The degree of inclusion will change depending on the idea of ​​the item, its goals, its highlights, the cross-departmental effort, and the coordination to achieve your versatile application.

Lack of marketing budget

Quickly mentioned above, advertising will play a key role in customer sourcing and development. Advertising for the application is extremely aggressive, and like any other element or management, your portable application should be developed with the goal of being effective. Very regularly, the advertising capacity is in retrospect an idea.

The cost of presenting your portable application should be considered from the beginning as you figure out what your wealth measurements will look like. Would you like to make a specific income measurement in the first half of the year? Do you measure the performance of a specific number of application downloads or clients in a given time period? Will customer loyalty with the portable application be at the level you expect?

The objectives are fundamental, but spending should be similar. In the event that you want to attract 15,000 customers in the main month, it is far-fetched that you can achieve this goal without having to pay the article. While you may not have correct numbers, you need to draw a line in the sand so you can benchmark, score, and refine.

Customer demand for constant updates

Continuous deployment is an important part of the continued success of a mobile app. Users are demanding, and as mobile technology evolves quickly, you can not expect to keep and delight users with a "set and forget" mentality.

As this is an ongoing approach, it must take into account support when planning a budget. Again, the numbers may not be accurate at first, but developing a longer-term strategy with a product roadmap (phased approach, rollout plan for new features, etc.) will give you a good overview of the effort and resources required ,

Know how to budget for your mobile app

The five issues discussed above are all the key factors in budgeting mobile apps. However, when budget proposals are made, they are often completely lacking, even though they are usually the most costly. If you did not consider them, you've budgeted for only a small portion of your project, not a fully functional, maintainable mobile app.


DreamProxies - Cheapest USA Elite Private Proxies 100 Cheapest USA Private Proxies Buy 200 Cheap USA Private Proxies 400 Best Private Proxies Cheap 1000 USA Private Proxies 2000 USA Private Proxies 5000 Cheap USA Private Proxies ExtraProxies.com - Buy Cheap Private Proxies Buy 50 Private Proxies Buy 100 Private Proxies Buy 200 Private Proxies Buy 500 Private Proxies Buy 1000 Private Proxies Buy 2000 Private Proxies ProxiesLive.com Proxies-free.com New Proxy Lists Every Day Proxies123.com Proxyti.com Buy Quality Private Proxies