The feed is fast until it is popular
A timeline that queries everything on every scroll is fine with two hundred users and unusable with twenty thousand. This is the single most common reason a launch goes quiet.
5 products, each grown from client work.
Licensed, hosted and supported by the team that wrote them.
A timeline that queries everything on every scroll is fine with two hundred users and unusable with twenty thousand. This is the single most common reason a launch goes quiet.
Reporting, blocking and a queue somebody actually reads are treated as phase two. They are not — the app stores will ask, and your first bad actor will not wait.
Push is the cheapest way to bring someone back and the fastest way to get uninstalled. Without preferences and batching, the two are the same button.
Delivery state, read receipts, presence and ordering look simple until two people message on a weak connection. Retro-fitting this is close to rebuilding it.
Profiles, the feed, and one way for two people to reach each other — built properly and launched. Everything else waits until real people are using it.
Where an app exists and has slowed down. We profile what is actually slow rather than rewriting it, which is usually a small number of queries and one missing index.
Where the product is the matching rather than the posting — dating, marketplaces, communities with interest graphs. The ranking is the product and deserves the time.
There is no single number — it depends on how the timeline is queried, not how many people are on it. We have seen apps struggle at two thousand and others fine at two hundred thousand. The honest answer comes from looking at the queries, which takes an afternoon.
Yes. Both app stores ask how user-generated content is reported and actioned, and a launch without an answer can be rejected. It is also the week you least want to be building it.
Usually. The first piece of work is a read of the code and the database rather than a quote — if it is in a state where changes are safe, we will say so, and if it is not we will say that instead.
Tell us roughly how many users, what the feed does on a bad day, and whether anyone is reading the reports. That is usually enough to say where the problem actually is.
UNIT INVENTORY, SITE VISITS, BROKER PAYOUTS,...
FABRIC CATALOGUES, SPECIFICATION FILTERS, EX...
COLLECTION CATALOGUES, CERTIFICATION DETAIL,...
PLAIN-LANGUAGE CARE PAGES, CONSULT REQUESTS,...
RATE COMPARISON, BULK LABELS, UNIFIED TRACKI...
QUOTATION ENGINE, SUPPLIER COST SHEETS, DAY-...
GST INVOICING, LEDGERS, RECEIVABLES AGEING,...
VEET, REES, ESS, ELIGIBILITY CONTENT, COMMER...
ADMISSIONS, ATTENDANCE, FEE COLLECTION, TIME...
LIVE SCORES, FANTASY TEAMS AND CONTESTS, VID...
Nobody is at a desk right now, but this is not a dead end — leave your question and an email address and you will get a proper answer, usually the next working day.