Buy for a role that fits now. Wait for a requirement you can name.
Buy a retro handheld now when a documented current option fits the games, controls, physical view, ownership routine and complete budget you actually want. Wait or choose another documented device when an essential requirement remains unmet. Do not delay solely because an unspecified next generation might be better, and do not buy an unsuitable model merely to stop researching.
A possible future improvement is not the same as a missing present need. Separate what you want to do today from what you would like eventually, then define what evidence would change the decision. A useful wait has a condition, not just an endless search for the newest name.
R36S is a conditional compact-classic candidate: its description lists 3.5-inch IPS at 640×480, RK3326, 1GB DDR3L and a Linux-based retro gaming OS (ArkOS community firmware). Reviewed USD base references are 64GB $79.99 and 128GB $89.99. Compare R36MAX for wanted larger physical viewing: 4-inch IPS at the same 640×480, RK3326 and 1GB DDR3L, with 64GB $99.99 and 128GB $109.99.
Neither route promises every title, future software support or modern connected features. MAX's larger panel and either model's higher capacity do not become a stronger processing generation. Keep an essential missing capability outside a positive purchase verdict.
By iGameConsole Editorial Team · Canonical S/MAX descriptions and complete configuration references reviewed October 6, 2026. This is a purchase-timing framework, not a product roadmap, release forecast, price prediction or physical test.
The 30-second buy-or-wait verdict
Ask three questions: What will I actually play? What indispensable condition is missing? What verified change would make waiting worthwhile? If no essential gap remains and the selected offer fits your routine and budget, a current device can have a complete purpose without being the last handheld you will ever want.
If a required system, control, application, connection or display arrangement is not established, delay that recommendation. A rumor does not resolve the requirement, but neither does buying a familiar inexpensive device and hoping.
| Your position | Useful next step | Keep separate |
|---|---|---|
| A documented current option fits. | Confirm the selected offer and ownership plan. | Future novelty from present usefulness. |
| An essential capability is missing. | Find a documented suitable alternative or wait for evidence. | A wish from confirmed support. |
| Your existing setup already serves the role. | Keep using it until a meaningful new role appears. | Interest from a purchase requirement. |
| You have not identified wanted play. | Clarify the activity before choosing a release date. | Researching devices from deciding a purpose. |
1. Start with a present-tense playing purpose
Write what you expect to use the handheld for in an ordinary week: an identified classic adventure, a few personal-score attempts, a reading-led campaign or a portable alternative to your home setup. Choose a purpose that survives a product announcement.
This is not a demand to have a permanent collection plan. You need enough specificity to judge the first meaningful role. “The newest retro device” describes an object; “this game during this routine” describes why to own it.
If you cannot identify the role, pause the device race rather than automatically ordering or waiting for a launch. The first-handheld play-preference guide addresses that earlier discovery step.
The timing decision starts after there is a useful purpose. Otherwise each new announcement can restart an unresolved question about what you enjoy.
2. Separate essential conditions from possible improvements
An essential condition determines whether the purchase serves its purpose. A preferred improvement can make a suitable role nicer without being required. Put each feature in the correct category before comparing current and possible future options.
If your target requires a particular application, controller method or connection, do not demote it merely because another device looks affordable. Conversely, an optional larger view need not become an indispensable future feature just because a new panel is discussed.
A useful requirement statement names the task and consequence: “I need this control because this action is central,” or “I want this larger physical view because I prefer it for this interface.” It should explain more than a spec-sheet preference.
Keep a separate list of interests you might explore later. Future curiosity is legitimate, but it should not silently turn a modest present purpose into a universal-device requirement.
3. Distinguish three meanings of waiting
You may be waiting for a missing capability, for reliable evidence about an announced option, or simply for a better moment in your personal budget and routine. These are different decisions and need different stopping conditions.
Capability-led waiting ends when the required task is documented on a suitable configuration. Evidence-led waiting ends when the relevant unknown can be answered. Personal-timing waiting ends when the actual circumstances make the purchase sensible.
“Wait until everything is better” supplies no decision boundary. The next option can also have tradeoffs, unanswered questions and another rumored successor.
Do not assign a date or deadline when none is verified. A clearly stated condition can be useful even when its completion date is unknown.
4. A roadmap name is not a complete purchase option
A possible model name, concept image or rumored feature is not a selected configuration with verified behavior, price, contents and terms. Separate discussion about a device from the evidence needed to buy it for a specific task.
An announcement can establish that something has been announced without proving every claimed experience. A spec sheet can establish listed specifications without measuring your target game or ownership routine.
A relevant observation needs the actual unit, setup and task. An available purchase offer needs its actual selected option and terms. These layers can progress separately; one does not automatically supply the others.
This guide identifies no upcoming S, MAX or other product launch. It makes no prediction about dates, features, future support, discounts or market pricing.
5. Build an evidence ladder for the change that matters
Use the weakest evidence only for the conclusion it supports. A rumor introduces a possibility. An identified official description supports the described specification. A scoped demonstration supports the observed task. A delivered-unit check supports your actual arrangement.
Do not collapse those stages into “confirmed better.” Also avoid treating every unknown as a reason that a future option must fail. Unknown means the recommendation remains conditional.
Ask what new information would answer your essential question. If it is input mapping, another glamour photo may add nothing. If it is the full cost, a chipset comparison does not supply the checkout total.
The gameplay-video evidence guide helps scope a demonstrated result. Normal footage is not automatically a laboratory measurement or every-title certificate.
| Stage | Use it for | Do not convert it into |
|---|---|---|
| Unverified discussion. | A question to investigate. | A committed product feature. |
| Identified product description. | Listed hardware and option facts. | Every-game performance or personal comfort. |
| Scoped ordinary-play observation. | The shown action on the stated setup. | All modes, measured latency or permanent support. |
| Selected current offer. | Option, stated contents and relevant terms. | Automatic availability or future pricing. |
| Your low-stakes validation. | The actual routine checked. | Loss-proof progress or universal compatibility. |
6. Newer can change a different thing from the one you need
A future device may be discussed in terms of screen, shape, processing, controls or software. Identify which change would affect your actual task rather than letting a new model number stand in for the answer.
A larger physical screen can be a desired viewing difference. More storage can be useful room. Neither automatically supplies stronger processing, a missing input method or a supported application.
Similarly, a processing specification does not answer every connection, original-controller or progress question. Follow the complete task rather than one impressive component.
It is possible for a device to be newer and still not be the best fit for your defined role. That is a decision principle, not a verdict about an uninspected future model.
7. A current classic role need not expire with a new announcement
If an identified classic, wanted controls and suitable physical format are the purpose, a new model announcement does not itself remove that purpose. Judge whether the actual unit continues serving the task.
This does not promise indefinite hardware life, software updates or repair support. It separates present usefulness from the fact that other products can exist.
A buyer may reasonably keep using a suitable current device without claiming it wins every specification. Another buyer may need a different role that it does not meet. Both choices can be consistent.
Do not buy on an unsupported “forever future-proof” claim. Equally, do not treat “not future-proof” as evidence that a well-matched current classic role has no value.
8. Your existing setup changes the value of waiting
If you already have a suitable way to play, waiting can mean continuing an activity rather than missing it. Identify what the contemplated handheld would add: portability, physical controls, a separate personal device or another actual role.
If you do not have a suitable setup, a documented current option may enable a wanted activity sooner. That is a personal use decision, not a calculated monetary return supplied by this guide.
Do not assign an invented value per hour or claim a universal cost of waiting. Your interest, available time and alternatives determine whether delayed ownership matters.
A current working setup also protects you from buying an unsuitable interim model. The choice is not always “buy this today or have no gaming.”
9. First ownership and replacement have different stopping rules
A first buyer needs a suitable entry role and a realistic preparation plan. An existing owner needs to identify what the new purchase adds or replaces. A new generation is not automatically the answer to either.
If an existing device meets the role, specify the limitation that would justify replacement before monitoring every launch. If there is no material gap, continued use can be the complete recommendation.
If the existing device has a fault, separate diagnosis and applicable support from product timing. A rumor is not a repair plan, and an attractive current model does not diagnose the old unit.
This page provides no internal repair steps, warranty verdict or universal replacement threshold. It keeps the ownership purpose separate from those technical and policy questions.
10. A placeholder purchase deserves its own justification
Buying a temporary device while expecting another can be reasonable only when the interim role itself is wanted and the total plan is affordable. Do not present two purchases as automatically better value than one suitable purchase.
Consider preparation, learning, storage and ownership effort as well as the unit price. The second device can have its own instructions, compatibility conditions and arrangements.
Do not assume guaranteed resale, trade-in, future discounts or automatic progress transfer. If one of those assumptions is essential to affordability, resolve it before committing.
A current compact classic can remain a separate useful role after another purchase, but that is a purpose to articulate, not a guaranteed outcome or forced upsell.
11. Current price facts do not forecast future bargains
A verified base price supplies a current comparison reference. It cannot establish the next price, the lowest future offer or how a possible launch affects existing products.
Waiting for a personally affordable budget is different from predicting a discount. Set the amount you can responsibly spend and compare documented offers when appropriate.
Do not base a recommendation on an invented sale date, price floor or stock shortage. No future price movement or limited-time purchasing claim is made here.
If you compare alternatives, keep the actual configurations equivalent where relevant. A different capacity, package, destination charge or seller arrangement can make headline prices misleading.
12. Define the complete budget before the timing verdict
List the selected option and any essential additional items or charges. Use the actual offer and destination information instead of assuming that the base price is the complete cost.
Distinguish items already owned, confirmed inclusions and unconfirmed needs. A photograph of a cable, booklet or protector does not supply a current order manifest.
Do not create a universal percentage for hidden costs or a made-up accessory allowance. The right total depends on the actual selected arrangement.
Affordability can legitimately lead to waiting even when the hardware is suitable. A technically correct recommendation is not a reason to pressure a buyer beyond a comfortable budget.
13. A personal date is not a verified delivery deadline
A trip, birthday or holiday can explain why timing matters. It does not establish that any selected order will arrive by that date.
Confirm applicable delivery information through the actual offer and support route. This guide supplies no destination estimate, dispatch promise or gift-arrival guarantee.
A rumored future release is especially weak evidence for a fixed personal occasion. If a deadline is indispensable, evaluate documented current options and their actual terms rather than assigning a fictional launch-to-door schedule.
If the date cannot be supported, adjust the plan. An honest alternate gift or later purchase can be better than treating a hoped-for arrival as confirmed.
14. Gifts need the recipient's requirement, not the buyer's speculation
A gift buyer may be tempted to wait for a newer device while the recipient simply wants a suitable classic role. Another recipient may need a feature the current shortlist does not provide.
Identify the intended activity, needed view, preparation tolerance and essential functions. A newer name does not remove those questions, and a nostalgic picture does not answer them.
Do not guarantee every gift can be returned, exchanged or reconfigured. Confirm the actual applicable terms and essential contents separately.
For a younger recipient, an adult should review actual content and learn charging and operating instructions. No all-ages or zero-preparation promise follows from buying now or waiting.
15. Separate future capability from future software support
A device specification, a software project and ongoing support are different. Current community firmware does not certify indefinite updates, a future feature roadmap or compatibility with every later release.
The S/MAX descriptions identify a Linux-based retro gaming OS (ArkOS community firmware). Exact firmware can vary by batch and later updating or re-flashing; use instructions that match the delivered arrangement.
Do not assume a future update transforms a physical limitation or implements an undocumented platform. Conversely, do not claim unsupported absence for every possible configuration.
If a particular update or software feature is indispensable, treat it as a requirement to verify, not a bonus already included in the purchase.
16. Future migration is not part of the price by default
If your plan includes moving progress to another device later, establish what data and software arrangements are involved. Native saves, emulator states, settings and storage layout need not have identical portability.
Do not assume moving a card transfers everything or that separate units share cloud accounts, profiles or automatic synchronization. A potential future model is not an established migration destination.
Protect valuable permitted records appropriately and verify supported transfer with disposable progress before relying on it. More nominal room on the same card is not independent protection.
A current purchase can still be worthwhile without a guaranteed migration route, but that limitation must be acceptable to the buyer rather than hidden behind an upgrade plan.
17. Choose R36S for a suitable compact role, not a roadmap
R36S lists 3.5-inch IPS at 640×480, RK3326, 1GB DDR3L and a Linux-based retro gaming OS (ArkOS community firmware). Its canonical classic direction includes NES, SNES, GBA and PS1 with individual conditions.
Consider S when the identified games, mapping, compact view and ownership routine fit the purpose you want now. A complete modest role is enough; it does not need a claim of universal longevity.
N64 and PSP behavior varies by title and configuration. Do not make S a PS2, Android-app or confirmed connected-feature purchase direction.
A date-based argument cannot resolve an unsuitable task. If the exact required game or feature is unverified, keep the recommendation conditional regardless of the entry price.
18. Choose R36MAX for wanted larger physical viewing
R36MAX lists 4-inch IPS at 640×480 with RK3326 and 1GB DDR3L. Compare it when more physical viewing area matters for the actual interface or preferred presentation.
MAX does not add listed pixels or establish a stronger processing generation relative to S in this comparison. Its larger display does not itself resolve an unsupported system, controller mode or connection.
N64 and PSP remain title- and setup-dependent. No PS2, Android or universal wireless route is certified here.
If you want compactness and the task fits S, there is no need to invent a larger-screen requirement. If the larger view is the benefit you actually want, assess it as that benefit rather than a future-proofing package.
Hardware facts versus timing assumptions
| Condition | R36S | R36MAX | Buying meaning |
|---|---|---|---|
| Panel. | 3.5-inch IPS | 4-inch IPS | Compact versus wanted larger physical viewing. |
| Resolution. | 640×480 | 640×480 | No extra listed source-view pixels. |
| Chipset and memory. | RK3326 / 1GB DDR3L | RK3326 / 1GB DDR3L | No stronger listed tier established. |
| System direction. | Linux-based / ArkOS community firmware | Linux-based / ArkOS community firmware | Actual firmware and task still need matching. |
| Future launch or price. | No forecast here. | No forecast here. | A purchase purpose, not a roadmap wager. |
| Essential target behavior. | Exact release and configuration matter. | Exact release and configuration matter. | The date cannot replace compatibility evidence. |
19. Compare actual capacity and price choices
| Option | USD base | Relevant role | Not supplied by the price difference |
|---|---|---|---|
| S 64GB | $79.99 | Suitable compact classic entry role. | Every title or future feature. |
| S 128GB | $89.99 | Compact role with useful nominal room. | Stronger processing or safer records. |
| MAX 64GB | $99.99 | Wanted larger physical view. | New processing generation. |
| MAX 128GB | $109.99 | Larger view and useful room. | Future-proof support or automatic migration. |
Within a model, $10 buys a different nominal-capacity option in the reviewed matrix. At matching capacity, MAX is $20 more with larger physical viewing as the relevant documented distinction. Choose that benefit only when it matters to the intended user.
S lists Purple, Black, White, Red, Yellow, Green and Blue in both capacities. MAX lists Black, White, Blue, Gray and Red in both. Finish is an appearance preference, not a processing or future-support tier.
Nominal capacity is not a manifest, performance grade or independent backup. Actual available space depends on arrangement and supplied files. Verify an essential title, package and lawful access separately.
These dated USD base facts are not fresh stock checks, complete destination totals or future-price predictions. Review the live selected option and applicable charges; local converted amounts need not use USD price endings.
A suitable current role is a reason to compare, not a reason to rush.
Review S when compact classic play fits, or MAX when the larger physical view is wanted. If an essential capability remains unverified, resolve it before ordering either.
20. Four buyers can reach four reasonable conclusions
The buyer with a clearly suitable classic purpose
The wanted release, controls, view and ownership routine fit a documented current option. Compare the actual offer without requiring that it win every future specification.
The buyer with an essential unverified feature
The purpose depends on a particular system, application, connection or input. Verify a suitable alternative or wait for evidence rather than hoping an unsuitable interim device changes.
The owner whose current setup already works
A new handheld has not yet added a meaningful role. Continued use is a complete outcome; interest in launches does not create an obligation to replace.
The buyer whose budget or routine is not ready
The technical option may fit while the personal timing does not. Wait for circumstances that make sense without predicting a sale or inventing a deadline.
These are illustrative purposes, not measured customer categories or conversion winners. The appropriate conclusion follows the actual requirement, not the most persuasive product label.
21. Set an evidence-based review trigger
Write a short decision note: “I want this activity. The current option meets these conditions. The unresolved requirement is this. I will reconsider when this specific evidence appears or when this personal circumstance changes.”
A review trigger might be an identified configuration demonstration, confirmed complete pricing or a genuine change in your own routine. It is not an unsupported date for a future release.
If no essential gap exists, decide whether a current role is worth the actual cost to you. If a gap exists, keep the condition visible. Repeatedly changing the requirement after each announcement makes every answer temporary.
There is no required number of research days. The purpose is a useful stopping rule, not a sales countdown or an instruction to stop investigating a real uncertainty.
22. Ask a purchase-timing question that can be answered
“I want to play this release, platform and mode during this routine. My essential conditions are these; my optional preferences are these. Does this exact current model and selected arrangement meet the requirements? Please separate listed facts, observed behavior and unresolved points. I am considering waiting for this specific missing condition, not for an unspecified better device.”
Ask content, preparation, charges and applicable terms as separate questions where relevant. A correct chipset answer cannot supply all of them.
If someone recommends waiting, ask what verified change matters. If someone recommends buying now, ask how the actual task fits. Neither answer needs a claim that the option is universally best.
This gives support a bounded problem and gives you a reusable record. It does not promise a response time, guaranteed resolution or automatic service eligibility.
| Write down | Example form | Decision use |
|---|---|---|
| Present purpose. | This identified classic in this routine. | Defines why to own it. |
| Essential condition. | This specific native input or feature. | Prevents an unsuitable purchase. |
| Optional preference. | More physical viewing, if worth the difference. | Creates a real tradeoff. |
| Evidence trigger. | A relevant demonstrated task or documented offer. | Makes waiting actionable. |
| Ownership plan. | Actual preparation, useful progress and total budget. | Connects selection to successful use. |
If you buy, validate the role before relying on it
Match the delivered model, option and confirmed contents to the order. Identify actual firmware and use its instructions before changing mappings, files or storage.
With disposable progress, check the wanted release and relevant actions, useful view and supported stopping and later return. A successful launcher screen is less than the ownership task.
Keep valuable permitted records appropriately protected before changes. Avoid replacing working software merely to chase an unverified future feature. Do not remove active storage while running or writing.
If something does not match, record the actual conditions and use the applicable support route. This guide does not certify a remedy, return window or automatic eligibility.
If you wait, keep the requirement useful
Continue using a suitable existing setup when one is available. Keep a concise list of the real missing condition instead of collecting unrelated rumor specifications.
When new evidence appears, compare the complete task again. A changed feature may solve the gap while introducing a different budget, preparation or physical tradeoff.
Do not turn waiting into a commitment to buy the rumored option regardless of the eventual result. Waiting preserves choice; it should not predetermine the answer.
If your actual purpose changes, revise the requirement honestly. A new interest is a new decision input, not proof that the earlier suitable role was wrong.
The honest fit boundary
Consider a current S/MAX route when the identified classic task fits, the actual physical benefit is wanted, the complete cost is acceptable and the ownership routine is understood. No imagined future feature is needed to make that role work.
Wait, keep your existing setup or compare another documented device when an indispensable capability is unresolved, the role is not clear or the budget does not fit. A higher capacity, larger display or faster purchase cannot cancel a missing condition.
Unknown is neither supported nor universally absent. This page supplies a decision method, not an all-device compatibility survey or a claim that the current shortlist covers the entire store.
Choose the role you can explain. The answer can be buy, compare, continue using what you have or wait for a specific fact.
Seven steps to decide whether to buy a retro handheld now or wait
A proposed purchase-timing checklist, not a launch forecast or benchmark.
-
Define present wanted play.
Identify the actual activity, release and routine that give the device a purpose.
-
Separate essentials and preferences.
Keep indispensable features distinct from optional viewing, storage and future interests.
-
Review documented current fit.
Match the exact task and configuration without assuming newer names or capacity solve unsupported needs.
-
Assess the existing alternative.
Identify whether a current setup already serves the role and what a new handheld would add.
-
Confirm cost and ownership.
Check the selected offer, essential contents, preparation and applicable charges and terms separately.
-
Choose a concrete review trigger.
Wait for a named missing condition or personal change, not an undefined universal improvement.
-
Validate the decision safely.
If buying, check the delivered routine with disposable progress; if waiting, reassess when relevant evidence arrives.
Buy-now-or-wait retro handheld FAQ
Should I buy a retro handheld now or wait for the next generation?
Buy when a documented current option fits the wanted play, essential features, physical role, ownership routine and complete budget. Wait or compare another device when an indispensable condition is unresolved. An unspecified future improvement is not a complete decision rule.
Is a newer model automatically a better fit?
No. Identify which documented change affects the actual task. Screen, storage, processing, software and connections answer different requirements.
Does this guide predict the next R36S or R36MAX?
No. No future launch, date, specification, discount or software roadmap is established here.
What makes waiting useful rather than indefinite?
Name the missing condition and the evidence or personal change that would cause you to reassess. Waiting for every specification to improve has no clear stopping rule.
Should I replace a current setup that already meets my needs?
Not automatically. Identify a meaningful new role or actual limitation first. Continuing to use a suitable setup can be the complete recommendation.
Is a temporary handheld automatically good value?
No. The interim role and complete plan need to be worthwhile. Do not assume guaranteed resale, trade-in, future discounts or automatic progress migration.
Does R36MAX represent a stronger processing generation than R36S?
Not in this comparison. Both list RK3326, 1GB DDR3L and 640×480. MAX lists 4-inch IPS versus S at 3.5 inches, a physical-view difference rather than a stronger listed tier.
Does 128GB make the purchase future-proof?
No. Nominal room does not certify stronger processing, future software support, every title or independent progress protection.
Does a future launch guarantee current prices will fall?
No such forecast is provided. Compare documented offers and a comfortable complete budget without inventing a sale date or future price.
Can I rely on a future release for a fixed gift or trip date?
An unverified release is not a delivery plan. Confirm actual selected-offer timing and terms; this guide makes no arrival guarantee.
Will every unit use identical firmware and transfer instructions?
No universal arrangement is promised. Descriptions identify a Linux-based retro gaming OS with ArkOS community firmware; exact firmware can vary by batch, updating or re-flashing. Follow the actual setup and verify any required migration.
What price references and final rule does this guide use?
Reviewed USD base references are S64 $79.99, S128 $89.99, MAX64 $99.99 and MAX128 $109.99. Choose for a documented suitable role now or wait for a named essential condition. Confirm live options, contents and applicable charges separately.
Choose a useful present role, not an imaginary perfect future.
A suitable compact classic or wanted larger view can be a complete purpose. It does not need a forecast, invented urgency or a promise of permanent superiority.
If that role fits, review the current S/MAX options. If an essential requirement does not fit, preserve it and compare evidence before recommending a purchase.
Review suitable R36S configurationsCompare the larger MAX view
Evidence and editorial scope
Recent canonical S/MAX descriptions and complete fourteen-plus-ten variant records supply hardware, colors, capacities and dated USD base references reviewed October 6, 2026. These facts are reused, not presented as fresh stock checks, physical tests or future-roadmap access.
Wait and new-model searches were supplemented by upgrade and first-handheld searches and actual headings and relevant body of the existing MAX upgrade review and first-player guide. Searches do not prove complete absence. The upgrade review concerns a current model comparison; the first-player guide concerns discovering wanted play. This page concerns when documented present fit justifies buying and when a named unmet condition justifies waiting.
Older upgrade copy included unverified side-by-side tests, ratings, library equivalence, grip and runtime advantages and inconsistent prices. Those claims are not adopted here. Existing articles and products were not modified.
No named-title test, future product inspection, release forecast, pricing prediction, resale valuation, migration test or delivery validation was performed. Authentic previously inspected store images illustrate current devices and historical packaging, not proof of future features or selected contents.
Visible FAQ and proposed checklist match their markup without fabricated scores, stock, discounts or universal support. Clear answers and documented product facts support accurate understanding, not guaranteed priority or rankings from Muse, ChatGPT, Google, Shop or another surface.
The primary duty is selection with discovery links, evidence boundaries and purchase reassurance. The commercial hypothesis is fewer stalled or unsuitable decisions and more qualified product progression. No direct query demand, article-click baseline, complete attribution or contribution-cost data was retrieved for this topic; demand, conversion and profit remain to be measured.
Where available, compare qualified article-to-product progression, carts, checkout and order paths with support, refund and expectation-mismatch signals. Use seven-day operational checks, 28-day buying comparison and 90-day sparse-data context. Retaining a suitable existing setup or choosing not to buy can also be a correct reader outcome.
Saved publication, live presentation, search indexing, Catalog distribution and actual commerce results remain distinct. The current decision is about the user's verified task and complete offer, not private ranking knowledge or future product promises.
Buy for a role that fits now. Wait for a requirement you can name.
