u/ashkanahmadi

Hi

So we have a very seasonal business where there is a lot of demand from April to September and then it dies out. Clearly, our organic impression from March goes up a lot and then from September it goes down a lot.

We also uploaded a lot of blogs, fixed a lot of technical issues (wrong headings, broken links, chain redirections, increased internal traffic, improved SEO titles and descriptions, ....).

The issue now is that we cannot associate how much of increased visibility is due to those changes versus just general demand going up meaning that impression would have gone up any way even if we didn't touch anything.

So my question is how do seasonal businesses handle this issue?

Hi I made this basic button to test something.

Feel free to use it: https://codepen.io/AshkanAhmadi/full/pvNbjWP

Hi

One thing I always wondered is how to know if I add a new library, do I need to build again (for native code) or no. For example, I want to use the expo-keep-awake library in my production app.

I install it and it runs fine on my development build on my device but I'm not sure if I can just push an EAS update to production without breaking it because it might need some native code.

I usually don't see anything about this on the official documentation but my approach is: if I install and it runs fine without a major error when loading, it means I dont need to build a new binary and submit to app store.

Is that okay?

Thanks

Hi

I have a basic app where the user signs up and then can upgrade their account type for free by using a free random coupon that they have for example abc123

I have created 2 tables:

This is the coupon code status which has fixed items like Active, Redeemed and Disabled

create table public.coupon_code_statuses (
  id bigint generated by default as identity not null,
  name text not null,
  slug text not null,
  created_at timestamp with time zone not null default now(),
  updated_at timestamp with time zone null,
  constraint coupon_code_statuses_pkey primary key (id),
  constraint coupon_code_statuses_name_key unique (name),
  constraint coupon_code_statuses_slug_key unique (slug),
  constraint coupon_code_statuses_slug_check check ((slug ~ '^[a-z0-9]+(?:-[a-z0-9]+)*$'::text))
) TABLESPACE pg_default;

and this is the table that holds the coupon codes. This table would have about 100k unique codes. Each code can be used only 1 time to upgrade the account. When used, they cannot be used anymore.

create table public.coupon_codes (
  id bigint generated by default as identity not null,
  code text not null, -- it has unique constraint so it's indexed automatically
  expirates_at timestamp with time zone null,
  is_active boolean not null default true,
  coupon_code_status_id bigint not null default 1, -- 1 is Active
  created_at timestamp with time zone not null default now(),
  updated_at timestamp with time zone null,
  constraint coupon_codes_pkey primary key (id),
  constraint coupon_codes_code_key unique (code),
  constraint coupon_codes_coupon_code_status_id_fkey foreign KEY (coupon_code_status_id) references coupon_code_statuses (id)
) TABLESPACE pg_default;

I have also have a small function that receives the coupon code request from the app, looks up the code to see if it exists or no, and if its status is not disabled or redeemed.

I'm not quite sure how to approach the rest. What's the best way of storing who used which coupon code? Should I have a separate table like user_used_coupon_code and there I add a reference to the code and the user id, or should I add another column to the coupon_codes table like user_id that is initially null but gets filled out when it's used by the user?

Thanks

I understand it’s an old and classical piece but I was wondering if anyone has ever found a music sheet arranged for the classical guitar. If you know anything please let me now.

Thanks