You've probably stumbled across the name while hunting for a place to publish your research. Or maybe a supervisor dropped it into a conversation like it was common knowledge. International Journal of Computer Applications in Technology — IJCAT for short. Sounds official. Sounds like the kind of journal that's been around forever That alone is useful..
It has. Since 1998, to be exact.
But here's the thing most people don't tell you: longevity doesn't automatically mean it's the right fit for your paper. And "computer applications in technology" is a phrase broad enough to swallow half of computer science whole. So what does this journal actually publish? Who reads it? And is it worth your time — or your APC budget?
Let's break it down.
What Is IJCAT
Published by Inderscience, IJCAT sits in that practical, applied corner of computer science where theory meets implementation. It's not a venue for pure algorithms or abstract complexity proofs. The clue is in the name: applications. The editors want work that takes computational methods and puts them to work — in engineering, in industry, in real systems Practical, not theoretical..
No fluff here — just what actually works.
Think: software tools for manufacturing optimization. AI-driven fault detection in power grids. IoT architectures for smart agriculture. Cloud-based simulation frameworks. That kind of thing Not complicated — just consistent..
The journal is peer-reviewed, open access (with an article processing charge), and indexed in Scopus, ESCI (Emerging Sources Citation Index), and a handful of other databases. It's not in SCIE or SSCI — so if your institution only counts Web of Science Core Collection, this won't tick that box. Worth knowing before you submit That's the part that actually makes a difference. And it works..
Scope in plain English
The official scope reads like a laundry list: computer-aided design, computer-integrated manufacturing, expert systems, neural networks, genetic algorithms, simulation, visualization, virtual reality, distributed systems, mobile computing, and on and on. But in practice? The papers that get accepted share a common thread: **a concrete problem, a computational solution, and some form of validation.
Pure theory papers struggle here. So do "survey" papers unless they're exceptionally structured and critical. The sweet spot is applied research with a clear use case.
Why It Matters / Why People Care
If you're a PhD student needing a first publication, or a faculty member in a region where Scopus-indexed journals are the promotion currency, IJCAT shows up on the radar for a reason. And it's accessible. The review process isn't glacial. And the open access model means your work gets read — not locked behind a paywall your university forgot to renew.
But there's a flip side.
Because it's broad and accessible, the journal attracts a lot of submissions. So reviewers notice. incremental. The result? Acceptance rates aren't published, but editors have hinted in interviews that it hovers around 25–30%. A tweak here. A minor extension there. A mix of solid, practical papers and a fair number that feel... That's not "easy" — but it's not Nature either. So do readers.
For researchers in emerging economies, IJCAT has historically been a legitimate stepping stone. It's indexed where it counts for many national evaluation systems. And Inderscience's production turnaround — once accepted — is decent. You're not waiting a year for typesetting.
Who actually reads it
Practitioners. Because of that, engineers. Graduate students. That's why people building systems who need a referenceable method they can adapt. It's not a journal that theorists cite heavily. But if you've built a scheduling algorithm for flexible job shops and tested it on real factory data? This audience will find it.
How It Works (Submission to Publication)
The workflow is standard Inderscience. You register on their editorial manager, upload your manuscript (PDF for review, source files later), suggest reviewers if you want — though the editor has final say — and wait.
Timeline expectations
- First decision: 6–10 weeks is typical. Sometimes faster if reviewers respond quickly.
- Revisions: One round is common. Two rounds happen. Three is rare — at that point they usually reject.
- Acceptance to online publication: 4–8 weeks. Inderscience publishes articles online continuously (no "issues" in the traditional sense), so you get a DOI fast.
- Print: There is a print version, but it's largely symbolic. The online version is the version of record.
Manuscript requirements
- Length: No hard page limit, but 10–16 pages is the sweet spot. Over 20 pages and reviewers start asking for cuts.
- Structure: Standard IMRaD — Introduction, Methods, Results, Discussion. Plus a "Conclusions" section (separate from Discussion) and "References."
- Figures/Tables: High-res. Vector formats preferred. Color is free online — use it wisely.
- Code/Data: Not mandatory, but strongly encouraged. A GitHub link or Zenodo DOI in the "Availability of Data" statement helps.
The APC question
As of 2024, the article processing charge is $1,200 USD (or equivalent). Inderscience offers waivers for authors from low-income countries — check the current list on their site. Some institutions have membership deals that cover part or all of it. Ask your library before you submit That's the whole idea..
Common Mistakes / What Most People Get Wrong
1. Treating it like a dumping ground
"I'll just send it to IJCAT, they accept everything.If your paper is pure theory, or a literature review with no critical analysis, or a student project written up without novelty — it bounces. Also, " Famous last words. Because of that, editors screen for scope fit before sending to reviewers. The desk reject rate is real. Fast Which is the point..
This is where a lot of people lose the thread.
2. Weak validation
We're talking about the #1 reason for rejection after review. Think about it: "We propose a new method" is not enough. Consider this: you need: benchmark datasets, comparison with at least 2–3 baselines, statistical significance tests, and a real-world case study or simulation that mirrors realistic conditions. Think about it: reviewers here know the domain. They spot hand-waving Small thing, real impact..
Easier said than done, but still worth knowing.
3. Ignoring the "Applications" part
You'd be surprised how many papers spend 80% of the text on algorithm design and 2 paragraphs on application. Flip that ratio. The application is the contribution. The algorithm serves it. Structure your narrative accordingly.
4. Sloppy English
Inderscience doesn't provide heavy copyediting. If your manuscript reads like a rough draft, reviewers will flag it — and the editor may reject on language grounds alone. Pay for editing if you need to. It's cheaper than a rejection-resubmit cycle elsewhere The details matter here..
5. Citing only yourself (or your lab)
Self-citation is fine. Show you know the broader literature. Only self-citation is a red flag. Especially recent work — last 3–5 years. The field moves fast.
Practical Tips / What Actually Works
Frame the problem first
Start the introduction with the practical problem. In real terms, not "scheduling is hard. On top of that, " But: "In semiconductor manufacturing, dynamic job arrivals and machine breakdowns cause schedule deviations of 15–30%, leading to... " Then introduce your computational approach as the response. Reviewers love this. It signals applied relevance immediately Not complicated — just consistent. Worth knowing..
You'll probably want to bookmark this section.
Use a comparison table — but make it honest
Don't just compare on metrics
Use a comparison table — but make it honest
A well‑crafted table can instantly convey the novelty of your contribution. Crucially, avoid cherry‑picking metrics that only flatter your method; include a “‑” where your approach does not apply or where data are unavailable. Consider this: list the most relevant baselines, then populate the rows with concrete numbers — accuracy, runtime, memory footprint, or any domain‑specific KPI. Indicate the source of each benchmark (dataset, simulation parameters, hardware) in a footnote. Reviewers appreciate transparency because it lets them verify that the comparison is fair and that the claimed improvement is not an artifact of selective reporting That's the part that actually makes a difference..
Align your keywords with the journal’s taxonomy
Inderscience indexes papers using a controlled vocabulary. Scan the journal’s “Instructions for Authors” for the official keyword list and select terms that appear verbatim. Also, over‑general keywords such as “computer science” dilute discoverability, while overly specific jargon that does not match the index can hide your article from relevant readers. A balanced set of 4–6 keywords that captures both the methodological core and the application domain will boost visibility and reduce the chance of a desk reject for “mis‑matched topic”.
Real talk — this step gets skipped all the time.
Submit a concise, structured abstract
The abstract is the first thing the editorial board reads, and it also serves as the basis for many indexing services. Keep it under 250 words, and follow the conventional four‑sentence scaffold: (1) context/problem, (2) proposed solution, (3) main results, (4) significance. And avoid abbreviations that are not defined in the main text, and do not include citations. A clear abstract speeds up the review process and reduces the likelihood of a “insufficient information” desk rejection.
Choose the right track for your manuscript
Inderscience offers several publication tracks — regular articles, short communications, and special issues. If your work extends a previous conference paper, verify that the conference’s “no‑duplicate‑publication” policy permits the journal submission; otherwise, request a waiver. Short communications are ideal for preliminary results that merit rapid dissemination, but they require a clear statement of why the findings are novel compared with existing literature. Selecting the appropriate track prevents unnecessary administrative back‑and‑forth It's one of those things that adds up..
Prepare a reliable response letter
When reviewers raise concerns, a systematic response format is essential. Attach a clean, annotated version of the manuscript that highlights all changes. Even minor typographical fixes should be mentioned; reviewers often interpret meticulousness as a sign of rigor. Worth adding: address each comment with a line‑by‑line reply, referencing the exact location (page, paragraph, figure) where the revision was made. A well‑organized response can turn a “major revision” into a “minor revision” and accelerate acceptance But it adds up..
This is where a lot of people lose the thread.
put to work the supplementary material
Inderscience permits supplementary files — code repositories, additional plots, or extended datasets. Use this space for details that would otherwise clutter the main text, such as full algorithm pseudocode, hyper‑parameter sweeps, or raw experimental logs. see to it that each supplementary file is referenced in the manuscript and given a clear caption. This not only satisfies the reviewers’ requests for transparency but also strengthens the reproducibility of your work.
Final checklist before clicking “Submit”
- Manuscript adheres to the journal’s formatting template (margin, font, reference style).
- All authors have approved the final version and signed the copyright declaration.
- Conflict‑of‑interest statement is completed, even if the answer is “none”.
- Data availability statement includes a persistent identifier (DOI or repository link).
- Keywords are drawn from the journal’s official list and reflect both method and application.
- Abstract, title, and keywords are free of grammatical errors and jargon.
Conclusion
Publishing in International Journal of Computer Applications and Technology is achievable when the manuscript is framed as a solution to a concrete, real‑world problem, substantiated by rigorous validation, and presented with scholarly precision. By respecting the journal’s scope, adhering to its stylistic and procedural requirements, and proactively addressing common pitfalls — such as weak validation, superficial application descriptions, and language issues — authors can markedly improve their chances of acceptance. The combination of a disciplined submission workflow, transparent reporting, and a clear articulation of impact forms a reliable pathway from initial idea to published research in this venue.
